Re:How Mailinator compresses its email stream by 90%
by pkulak on Wednesday February 22, 2012 @01:34AM
(#3619729)
But if you have a Redis cache on the same box (he says he only has one box anyway) it's still in the same category: "Main physical memory", with maybe some communication overheard.
Re:How Mailinator compresses its email stream by 90%
by willvarfar on Wednesday February 22, 2012 @08:31AM
(#3620753)
Re:How Mailinator compresses its email stream by 90%
by willvarfar on Wednesday February 22, 2012 @05:31AM
(#3620291)
"maybe some communication overheard" is orders of magnitude slower than L1/L2.
Hmm, there is something very wrong here. I'll try and explain in a blog post.
Re:How Mailinator compresses its email stream by 90%
by pkulak on Thursday February 23, 2012 @02:26AM
(#3624138)
But we're not talking register caches. 800 megs stashed in a giant Java hash are not going to be in L1 or L2 cache.
Re:How Mailinator compresses its email stream by 90%
by willvarfar on Thursday February 23, 2012 @04:47AM
(#3624372)
http://williamedwardscoder.tumblr.com/post/18065079081/cogs-... might be interesting
CPU registers (8-32 registers) – immediate access (0-1 clock cycles) L1 CPU caches (32 KiB to 128 KiB) – fast access (3 clock cycles) L2 CPU caches (128 KiB to 12 MiB) – slightly slower access (10 clock cycles) Main physical memory (RAM) (256 MiB to 4 GiB) – slow access (100 clock cycles) Disk (file system) (1 GiB to 1 TiB) – very slow (10,000,000 clock cycles) Remote Memory (such as other computers or the Internet) (Practically unlimited) – speed varies