Date: 03/30/00
- Next message: Kristian Koehntopp: "Re: [PHPLIB] Too long session.val with PHP4.0RC1"
- Previous message: Gary Bickford: "Re: Fwd: Re: [PHPLIB] Re: [PHP3] persistent data"
- In reply to: nicholas klem: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Next in thread: Gary Bickford: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Reply: Gary Bickford: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Reply: Sascha Schumann: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In netuse.lists.phplib you write:
>Thanks! A good thing to know. Maybe we could balance the load
>between mysql and CT_Shm and see which breaks first? Anyone
>know of good ways to stress-test mysql and/or php? Could be
>fun. ;-)
Storing sessions in MySQL will effectively store them in server
memory, unless you chose your MySQL buffer size near zero. Using
MySQL adds some overhead due to context switches and
interprocess communication, but if you connect using
"localhost", MySQL will usually use a Unix Domain Socket or
Windows Named Pipe instead of an TCP/IP Socket to communicate,
which is much, much faster. On Linux, Unix Domain Socket speeds
approach shared memory speed for small session sizes.
Kristian
-
PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in
the body, not the subject, of your message.
- Next message: Kristian Koehntopp: "Re: [PHPLIB] Too long session.val with PHP4.0RC1"
- Previous message: Gary Bickford: "Re: Fwd: Re: [PHPLIB] Re: [PHP3] persistent data"
- In reply to: nicholas klem: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Next in thread: Gary Bickford: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Reply: Gary Bickford: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Reply: Sascha Schumann: "Re: [PHPLIB] Re: [PHP3] persistent data"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

