Forum Moderators: coopster
This might also help. It contains great information about optimizing your tables. :)
Why not store a string with the location of the pic instead fo the pic itself?
Or you could still store the pics in a table, but on there own, with nothing else and just refer to there primary key when retrieving the one/s you want.
So maybe you have something like:
TABLE pic_info
PRIMARY KEY
name string
height int
width int
alt string
blob_pk int --Foreign key for pic_blob table
TABLE pic_blob
PRIMARY KEY
pic blob
However most of the problem is probably coming from phpMyAdmin (as henry0 pointed out), as it is loading the whole table into memory before you can look through it. So on the command line you, so long as you dont do SELECT *, you can get just the information that you require.
So I guess that splitting the table is an easy way for you to be able to continue to use phpMyAdmin, or use the command line and dont split the tables.
because its out from mysql so at a time may be there are 1000 visitors browsing that pages ...