Database contention due to url callback (fixed on 6.x)
| Project: | Javascript Countdown Timer |
| Version: | 5.x-1.21 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I've just installed this module on a "big" (said about 500.000 registered users, 150.000 pageviews/day) community and I've noticed an inmediate performance hit.
Reading the logs I've seen on every page request a user made there is an access to /countdowntimer/timerjs recorded in the access logs (not the watchdog), I think this is not aceptable in our conditions (it doubles the number of inserts on the access_log table), so we will pobably make a copy of the generated js file in order to get it cached by browsers.
Is ther any other workaround in order to avoid that inserts?
(I'm not a coder, just a sysadmin) There is no other way to pass variables values to javascript without having to generate the whole javascript on every page load?
I hope there could be a quick fix for this. Tanks in advance. BR
#1
Could jquery help in fixing this?
#2
Not so much jquery as the 6.x branch. We moved away from the drupal callback in favor of an actual
.js file. This let's the browser use its normal cache, and helps the database quite a bit. This hasn't
been backported to the 5.x branch.
#3
Ok, thanks for your support.
I close the issue since i think this won't be backported to 5.x
BR
#4
Automatically closed -- issue fixed for 2 weeks with no activity.