Comments on: Memcache and shared hosting.

By: Nacho

Nacho — Fri, 04 Jun 2010 23:37:16 +0000

Honestly, I think you’re wrong. The reason I want to use memcached in my shared hosting is as simple as the fact that, by using it, I can avoid paying for a more powerful (and expensive) dedicated hosting.

By: Snowcore`

Snowcore` — Wed, 09 Dec 2009 16:12:14 +0000

I am using simple file caching on the shared hosting. But only for small projects. Really, big project needs dedicated, or at least virtual server

By: Martijn

Martijn — Thu, 05 Mar 2009 21:53:42 +0000

Well, of course memcache(d) is used for more larger(or read heavier) applications.
Very handy when it comes to object caching resultset’s and so on.

File storage could also be used but:
- it’s VERY slow when u look at the performance compared to memcache(d)
- u should make a good file locking mechanisme when u push/pull to/from 1 file

Sometimes in small applications u need HIGH performence and easy access for low traffic applications.

Like:
JS Ajax chat that push and pulls messages.(wich i made)
An problem appears when u would like the chat-messages to exists like 3 seconds.

I just build it to use the file handler (mysql). But when u install the chat on a server that uses memcache(d), it automaticly uses memcache(d).

But u can assign memcache(d) to a “user”… right ^^

By: Pascal

Pascal — Fri, 27 Feb 2009 06:01:05 +0000

Actually, one of the conveniences of memcaching is that you can store resources like result sets. If you wanted to do this with file storage, you would need to take each row of the result set, turn it into an array, serialize it and store it. Then do all that in reverse to get it out again.