Msg#: 3836102 posted 10:17 am on Feb 1, 2009 (gmt 0)
If they are pics then not much point in compressing, assuming you are storing them as jpeg (or something similar) not in raw format.
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.
Msg#: 3836102 posted 2:12 pm on Feb 1, 2009 (gmt 0)
i don't want to use the phpmyadmin its just an admin place actually the problem is when i try to use from phpmyadmin so its take much time to show me the 30 rows then 30 then so on.... i just want to confirm is the php script also take that much time like 1-2 mins etc... if yes then how much images per page will be the best choice ?
because its out from mysql so at a time may be there are 1000 visitors browsing that pages ...