Hi Andrew, DSpace does send several requests per page to the REST API to gather all the data it needs to fill out the page. The number of requests, however, differs based on the page data and how many objects you're displaying on the page, and which features you have enabled.
However, each request is cached. So, on your first visit to the site, you may have a larger number of requests to gather information...and then that information is cached (in your browser) and other pages no longer need to make the same requests. I'm not familiar with any page which involves 80 requests at once. Most pages make <10 requests to draw the page (and often <5). Some administrative or submitter tools may use more, but public pages tend to have fewer requests. You can see that behavior on our Sandbox site at https://sandbox.dspace.org/ , where you can "watch" the requests per page by opening up your Developer Tools in your browser and looking at the "Network" tab. If you've found a single page that is generating 80+ requests, then that sounds like a bug that should be reported to https://github.com/DSpace/dspace-angular/issues (We'd need details though on how to reproduce the behavior, etc) That all said, SSR (server side rendering) can be a performance bottleneck at times when a large number of bots are hitting the site. We do have a number of "Performance Tuning" tips in the documentation that can help to cache pages for bots or *limit which pages do SSR* (which can block bots from accessing those pages): https://wiki.lyrasis.org/display/DSDOC9x/Performance+Tuning+DSpace If you use some of those tactics, you should be able to lessen the server load from some (better behavior) bots. However, I'll admit, the AI bots these days are a lot "smarter" and more aggressive. These can be difficult to deal with (and it's not just DSpace that has issues with these aggressive bots -- all repository systems do). There is no "silver bullet" for the aggressive, AI-related bots. But, we have a "discussion ticket" open where we link to resources, and other developers have shared tips on what works for their DSpace: https://github.com/DSpace/dspace-angular/issues/4565 There's not a single solution in this case though, and it often requires installing tools *around* DSpace to help manage the bad-behaving bots. Hopefully this gives you some resources to get started. Tim On Wednesday, February 4, 2026 at 11:11:29 AM UTC-6 [email protected] wrote: > Hi, > > I analyze my dspace server logs regularly, both dspace and apache. > For instance, yesterday there was 5.7M events in apache log (5M from bots, > though) > I could not help notice that all top requests are service: > > 145837 /server/api > 144840 /server/api/authn/status > 144102 > /server/api/authz/authorizations/search/object?uri=...&feature=isCommunityAdmin&embed=feature > 144099 /server/api/authz/authorizations/search/object?uri= ... > &feature=administratorOf&embed=feature > 144088 /server/api/authz/authorizations/search/object?uri= ... > &feature=isCollectionAdmin&embed=feature > 144031 /server/api/authz/authorizations/search/object?uri= ... > &feature=canSubmit&embed=feature > 143820 /server/api/authz/authorizations/search/object?uri= ... > &feature=coarNotifyEnabled&embed=feature > 143704 /server/api/authz/authorizations/search/object?uri= ... > &feature=canEditItem&embed=feature > 143670 /server/api/system/systemwidealerts/search/active > 143640 /server/api/authz/authorizations/search/object?uri= ... > &feature=canSendFeedback&embed=feature > 143638 /server/api/authz/authorizations/search/object?uri= ... > &feature=canSeeQA&embed=feature > 143512 /server/api/core/sites > 143495 /server/api/discover/browses?size=9999 > 143486 /server/api/config/properties/contentreport.enable > 143486 /server/api/authz/authorizations/search/object?uri= ... > &feature=epersonForgotPassword&embed=feature > 143482 /server/api/authz/authorizations/search/object?uri= ... > &feature=epersonRegistration&embed=feature > 143311 /server/api/authz/authorizations/search/object?uri= ... > &feature=canManageGroups&embed=feature > 137268 /server/api/config/properties/submit.type-bind.field > 117537 /server/api/discover > 117057 /server/api/discover/search > 116703 /server/api/config/properties/websvc.opensearch.enable > 116564 /server/api/config/properties/websvc.opensearch.svccontext > ...and so on. > > I just opened an item page and watched 80+ requests to from my IP in the > log! > So I figure out that the real view count was 100K a day. > > At the same time, the server's Core Web Vitals are barely OK. Actually, > all pages are fast on the desktop and slow on the phone. > > So the question is: > Is that absolutely nesessary to have 80+ server requests per page? > Does it make sense to ask for authorizations more than once for an > anonymous user? Pardon my ignorance. > > Thanks, > Andrew > -- All messages to this mailing list should adhere to the Code of Conduct: https://lyrasis.org/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-devel/3a8481ef-992c-4ec8-accd-bbbd676c2961n%40googlegroups.com.
