-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kasthuri Ilankamban wrote:
[snip]
>
> The table that's it's complaining about is a session table which
> stores web session information. Basically the data in that table is a
> throw away data and gets deleted when the user logs out. The session
> data column in that table is defined as long blob. The average length
> of the row is not that big but once in a while application inserts a
> row for a user with session data that could exceed 200MG . Since we
> have lots of concurrent users and if application inserts few rows
> with > 200MG data simultaneously innodb runs out of memory and
> crashes. Eventhough we have 8 gig memory, I'm not able to start
> mysql if I allocate more than 2Gig to innodb_buffer_size. Do you know
> how I can allocate more than 2 Gig memory to innodb on 32 bit
> machine. That might solve our problem.
[snip]
Kasthuri,
Maybe it's time to re-think your application architecture? A 200-meg
BLOB is quite large for a highly-concurrent system, considering that
MySQL will have to read/save it in its entirety _and_ allocate network
buffers for it, so essentially you're allocating _400_ megs or so _per_
client.
(not to mention that many of your web sessions are sending 200 megs of
data around your network between your appserver(s) and your database,
which is a performance issue as well)
-Mark
- --
Mark Matthews
MySQL AB, Software Development Manager - Connectivity
www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD4DBQFCzBgMtvXNTca6JD8RAhPYAKDDqEMlqXKM1q+cEkj2DTUcR795EQCY4h8J
xIIf3/Uyktd0PO5M6573qw==
=gWXC
-----END PGP SIGNATURE-----
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
