You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
Hi Nick
Quick query(1 of 2), we previously discussed/agreed it would be better for me to run a crontask via the server every 5 minutes that starts /utilities/runcron.php as I had a stock update cron job that takes around 30 seconds and may have delayed a user if they were the hit the site and run the half hourly crontasks.
This all works correctly as the crontasks are run in the background with automatic execution turned off.
I have noticed that the CORE_Sessions table contains around 20000 rows when I am the only person who visits it and search engines are blocked.
A row is created every 5 minutes when the cron task is run, and a row is created for every subsequent task that may need to be run.
Over a month, this creates around 20000 extra rows in the database.
Just want to check this is the expected behaviour and the extra rows are nothing to worry about.
Thanks
Rob
Offline
9.0.2
It must be 9.0.2 as the sessions are KS based, not sid's
Last edited by zanart (09-24-2018 07:38:39)
Offline
Basically blank, other than my VAT display value which is set every new session
a:1:{s:10:"displayvat";s:4:"EXCL";}
Offline
I haven't checked, but I assume the automatic cron execution would also create a new session??
Edit: if I access /utilities/runcron.php, a new KS session row is created.
Last edited by zanart (09-24-2018 07:52:20)
Offline
This has something to do with my displayvat value being generate every session!
It doesn't happen if I remove the start up task that creates it.
Self inflicted and nothing wrong with kryptronic!
Offline
You've added 'displayvat' as a session var for every user. Guessing in another startup script. That's why cron is creating a session. Otherwise, it wouldn't save anything to a session (and in 9.0.2 and higher, no session would be created). Maybe only set that session var for non-cron requests, or even better, do it for non-cron requests and set a cookie instead of using a session var. In 9.0.2 we limited the use of the sessions table greatly, relying more on cookies to store things like your 'displayvat' variable. Maybe you should only set 'displayvat' when set by a customer, otherwise default it.
Offline
You are correct. The mod was just duplicated from V8 without much thought going into it.
Think I will change to cookie based.
Thanks for the pointers.
Offline