Home » Performance » MySQL » Commit latency for rows containing longblob columns..
Commit latency for rows containing longblob columns.. [message #169] Thu, 14 September 2006 23:29 Go to next message
rame
Messages: 1
Registered: September 2006
Junior Member
Hi,

I have two longblob columns in my table that might run into 4MB each at its peak. I see some latency while updating and committing these rows.

What I did is:

a) try committing these rows in one transaction
b) Once the transaction commit is returned back to the application, do a query using mysql client. (I use Java 1.5->Hibernate2.0->Mysql 5.1)
c) Though, I see the rows being populated - I don't see the longblob columns populated until sometime.

Is there any missing configuration that I need to set?

Any help is appreciated.

Thanks,
Ramesh.
Re: Commit latency for rows containing longblob columns.. [message #220 is a reply to message #169 ] Tue, 03 October 2006 17:51 Go to previous message
Peter  is currently offline Peter
Messages: 405
Registered: August 2006
Senior Member
Super Guru
Are you saying you have called commit from certain transaction and after commit has succeed you do not see values for longblob columns ?

This would be the bug. I would however try to create it using some simple script rather than Hybernate (Java test case is fine)


Peter Zaitsev, MySQL Performance Expert
MySQL Performance Blog - http://www.mysqlperformanceblog.com
MySQL Consulting http://www.mysqlperformanceblog.com/mysql-consulting/
Previous Topic:innodb_thread_concurrency values for many cpu systems
Next Topic:Performance optimisation for very large datasets
Goto Forum:
  


Current Time: Fri Jul 10 02:22:11 EDT 2009

Total time taken to generate the page: 0.04260 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 2.7.7.
Copyright ©2001-2007 FUD Forum Bulletin Board Software

MySQL is a trademark of Sun Microsystems.
InnoDB is a trademark of Oracle Corp.

Percona Performance Forums are a service of Percona, Inc.
Not affiliated with Sun Microsystems or Oracle Corp.