On Fri, Jun 26, 2015 at 8:16 PM, Michael Barton m...@weirdlooking.com
wrote:
What's the logical difference between having object data in memory on a
memcache server and having it in page cache on an object server?
+1 - about a syscall - i.e. not much - I think memcache does it's own heap
On Jun 25, 2015, at 7:35 PM, 杨苏立 Yang Su Li yangs...@gmail.com wrote:
Thanks a lot for your answer.
I guess that is an excellent answer on why does swift explicitly disable
object data caching at the page cache level. But my question is a bit
different Why doesn't swift use memcached
Excerpts from 杨苏立 Yang Su Li's message of 2015-06-25 17:35:18 -0700:
Thanks a lot for your answer.
I guess that is an excellent answer on why does swift explicitly disable
object data caching at the page cache level. But my question is a bit
different Why doesn't swift use memcached to cache
On Thu, Jun 25, 2015 at 7:35 PM, 杨苏立 Yang Su Li yangs...@gmail.com wrote:
I guess that is an excellent answer on why does swift explicitly disable
object data caching at the page cache level. But my question is a bit
different Why doesn't swift use memcached to cache object data? Not that
it
Hi,
I have noticed that even though account/container information is
cached using memcached in Swift, it doesn't cache any actual object
data.
Could someone enlighten me what's the consideration behind this
decision? Because it seems like it might be useful...
Thanks a lot
Suli
--
Suli
You're right. Caching object data is one way to really speed up reads to
content that is stored in Swift and accessed frequently. Often time, deployers
use existing tools like squid, varnish, or a CDN to do that.
But that still leaves the question why don't we cache the object data in
Swift?.
Thanks a lot for your answer.
I guess that is an excellent answer on why does swift explicitly disable
object data caching at the page cache level. But my question is a bit
different Why doesn't swift use memcached to cache object data? Not that
it is a bit different than implementing it yourself
