This depends entirely on how much physical and virtual memory you have available, how other applications are competing for that memory, how the OS responds to competing demands, and how fast your disks are (since you'll swap quicker with faster disks). Do note that any operation on that blob that will require a temporary copy will double your RAM hit.
There's no problem per se with sticking a hugh object into a hash.
In reply to Re: Storing a BLOB in a Hash
by dws
in thread Storing a BLOB in a Hash
by Wally Hartshorn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |