I was having corrupted the "sessions" table... I had to manually repair it... To my surprise... there were more than 400,000 entries and 98 Mb ... the biggest table in the database.... I have noticed that most of the entries are from ubercart modules.. I have emptied the sessions table... and in seconds.. I already have 10 more entries in the table.... what's going on ?
most of them by uc_cart_id

Why does it use the sessions table so much ? I think it can be a performance issue.

Comments

rszrama’s picture

Status: Active » Postponed (maintainer needs more info)

Not sure... we use the session table to track the cart ID for anonymous users, but they're supposed to expire. Are you running a high traffic site and do you have cron setup?

hedac’s picture

yes I have cron each hour

is it normal to have many sessions for the same ip?
most of sessions entries are from uc_cart_id
I have thousands of entries in the sessions table again...

like this

sid hostname timestamp cache session
18ac6e839c1ee908e9d72ed076e30f22 66.249.66.13 1248624955 0 uc_cart_id|s:32:"be3592341b88952915024dbc6b32ac9c"...
21fc39b574d079a125c919034c41a8de 66.249.66.13 1248625030 0 uc_cart_id|s:32:"a8b0ee237dc6e3825c44744377faca72"...
67a9e1a472571b55b653641c17167bc9 66.249.66.13 1248625195 0 uc_cart_id|s:32:"5418137719b3abd2ae71b40a9440d7a5"...
4024227374dd1db9680dee430d6d2a9f 66.249.66.13 1248625256 0 uc_cart_id|s:32:"eb1a5594d0aae31f08f2844a9de920fe"...
3cbfae163f45fd9be6219464c1e64706 66.249.66.13 1248625359 0 uc_cart_id|s:32:"063f9043d18213c8114663ebe04a6e32"...
7356cf13703d8d04e17aba6d9fd5b39f 66.249.66.13 1248625522 0 uc_cart_id|s:32:"bed6041007e8d4c7ab33804553af7d49"...
b3285e4d53ab061422a4ca47b969e0c5 66.249.66.13 1248625543 0 uc_cart_id|s:32:"042b11453c7d0872282169242409f9fa"...

Damien Tournoud’s picture

If you are on a Debian-based system, be careful about configuring session handling correctly (see for example #160046: Session Handling (garbage collection/expiry) fails under Debian).

TR’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Closing due to lack of response. I'm going to assume #3 and the issue cited there (plus all referenced threads) adequately addresses the problem.