Question

By counter it could be pageviews, downloads, number of votes etc. Basically, not very critical data.

What is the best way to store those information? Mysql is not a good option. What do you guys use?

Answer 1

I think I would go with Redis, because:

Antirediz(his nickname) is really actively developing Redis. (Every time when I look at my github dashboard he has commited some new code). He now is developing redis fulltime thanks to VMware
Redis is eventually persistent so the performance is kickass (first only uses memory which is fast).
Redis has an atomic increment operation which you need.
Redis has a a lot good PHP libraries. There is also one which is written as a C extension so it has really good performance. Redis website also has an overview off these extensions. Some are pure PHP code (run a litle but slower, but are easier to configure).

Answer 2

MongoDB with upserts is great for this.

If you re storing something like:

{ "url" : "www.example.com", "pageviews" : 0 }

you can atomically increment pageviews really quickly with the atomic operation $inc:

db.downloads.update({ url  :  www.example.com }, { $inc  : {pageviews : 1}})

If you use upserts, you don t have to check whether a document exists before updating it. For example, if you say:

db.downloads.update({ url  :  www.example.com }, { $inc  : {pageviews : 1}}, {"upsert" : true})

the document with the url www.example.com will be created if it doesn t exist (with pageviews set to 1) or, if it does exist, pageviews will be incremented. This means you don t have to worry about pre-populating the collection.

Answer 3

The famous view counters of the 1990s used simple files to store the number. If all you need is just to store one number, anything is good enough.

Answer 4

I would say APC or memcached are good choices.

友情链接