Re: Fastest way to check for an image in a table
Posted by:
Rick James
Date: September 26, 2010 09:17AM
Do the math...
5M images
32 bytes for a hex version of MD5
10 bytes overhead per index entry
5M * (32 + 10) = 200MB -- pretty small compared to today's typical RAM size.
Even if you had to hit the disk, do you really expect to be processing more than 100 images per _second_ ?
Let's do some more math...
5M images
100/sec
5M / 100 = 50K seconds -- that's less than one day.
Subject
Written By
Posted
September 24, 2010 01:57PM
September 24, 2010 03:10PM
September 25, 2010 08:15PM
September 26, 2010 04:00AM
Re: Fastest way to check for an image in a table
September 26, 2010 09:17AM
September 26, 2010 10:47AM
September 26, 2010 01:05PM
September 26, 2010 05:27PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.