Tuesday, May 05
Slow Samba
Scenario:
At my day job we have millions of images stored in a shared folder. Each of around 800,000 objects is represented by about 20 images in different sizes and formats.
This is shared internally over Samba, because it works for what we need.
Scenario:
At my day job we have millions of images stored in a shared folder. Each of around 800,000 objects is represented by about 20 images in different sizes and formats.
This is shared internally over Samba, because it works for what we need.
Except that for certain operations, that directory is horribly, painfully slow. Local access on the file server is just fine; it's only remote access.
To cut a stupid story short, the problem is that Unix is case-sensitive and Samba is case-insensitive. If you are looking for a file and Samba finds an exact match, it's as fast as you'd expect. But if you are looking for a file and it's not there, Samba will scan the entire directory for case-insensitive matches, which is a disaster if you have millions and millions of files.
Solution:
Create a specific share for that directory and set
Mount that in the appropriate place, and problem solved.
To cut a stupid story short, the problem is that Unix is case-sensitive and Samba is case-insensitive. If you are looking for a file and Samba finds an exact match, it's as fast as you'd expect. But if you are looking for a file and it's not there, Samba will scan the entire directory for case-insensitive matches, which is a disaster if you have millions and millions of files.
Solution:
Create a specific share for that directory and set
case sensitive = true.Mount that in the appropriate place, and problem solved.
Posted by: Pixy Misa at
12:37 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 162 words, total size 1 kb.
47kb generated in CPU 0.0151, elapsed 0.1109 seconds.
56 queries taking 0.0999 seconds, 339 records returned.
Powered by Minx 1.1.6c-pink.
56 queries taking 0.0999 seconds, 339 records returned.
Powered by Minx 1.1.6c-pink.
