Link to home
Start Free TrialLog in
Avatar of b0lsc0tt
b0lsc0ttFlag for United States of America

asked on

MySQL server config for table that has longblob field

I have a server that right now is pretty much just used for MySQL.  The DB has various tables but one of the main tables is one used for storing binary files in a longblob field.  The files can be anywhere from a few hunder KB in size to a few MB.  Another field is "program" and that is a always used in the query to get binary files just for the "program."  For the most common program the fields can be > 45 for a specific version and total 700+ records for that program.  A field "version" is also used to narrow down the results.  The "query" will just end up getting one record if any at all.

This is hosted on a Windows 2003 SBS server if that matters.

The problem is the "download" of the blob seems to be taking some time.  If the server is restarted, the number of records with the same program are lowered, or with "programs" that have fewer records and smaller binaries the download is at a normal speed.  What are configurations in the INI that would make the most difference in this type of DB and table?  What are status or server variables (in MySQL Admin) that will be especially useful in narrowing down problems that would cause this?  There are other uses for the server (e.g. web server) and DB (e.g. other tables with records that aren't blob fields) so let me know if those could be negatively impacted or factor into any of this.

I am familiar with MySQL but just not an expert in its set up, especially in a situation like this.  Let me know if you need any other info.  Thanks!

bol
ASKER CERTIFIED SOLUTION
Avatar of rydersaint
rydersaint

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of b0lsc0tt

ASKER

Ryder,
Thanks for the response.  I have made that change to that field (longblob to mediumblob).  Thanks for the input and recommendation on it.
Any other ideas or suggestions?  Let me know it some other details are needed.
bol
Avatar of rydersaint
rydersaint

ok so mediumblob then

I would recommend having two tables

one like

TABLE1
keyID (INT) --primary key | filelink (INT) | file (mediumblob) --your medium blob

and then another table in memory

CREATE TABLE TABLE2 (blah blah blah) ENGINE = MEMORY;

TABLE2
keyID (INT) --primary key | filelink (INT)| fileName (VARCHAR) -- name of your file | and so on

then select with a join like

SELECT * FROM TABLE1
LEFT JOIN TABLE2 ON TABLE1.keyID=TABLE2.keyID
WHERE fileName = 'the requested filename';

(* Note - you will need another table for table2 to copy from as all data leaves the memory table when restarting the server. Basically one for storage and one for selecting from)
Thanks for the response and additional suggestion.  I am interested in trying to use it but not real clear how the second table will help.  Is the "engine=memory" part the key to an improvement?  How or why does it help?
What is the purpose of the filelink field in each table?  Is that for some relationship or what?  The ID seems to be what you use for the JOIN.
Thanks for clarifying and the extra details.
bol
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
rydersaint,
Thanks!  I have held off responding or closing this because I was hoping to test it.  That won't be able to happen right away though so I won't leave you hanging.  I do appreciate your help and info.
bol
Thanks!
thank you for the points b0lsc0tt
let me know if you need any other info