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_
.
On 7/5/05, Kasthuri Ilankamban [EMAIL PROTECTED] wrote:
Hi, We are running mysql version 4.1.7 with innodb on i686 running
2.4.26 linux kernal with 8G memory. Mysql crashes consistently
during heavy usage with fatal innodb error. We are running a high
volume front end application which inserts
Hi, We are running mysql version 4.1.7 with innodb on i686 running
2.4.26 linux kernal with 8G memory. Mysql crashes consistently
during heavy usage with fatal innodb error. We are running a high
volume front end application which inserts 50M data to a row in
innodb table often. I don't