mrkris - Latest Comments

Re: A new beginning

mrkris — Tue, 30 Apr 2013 16:14:13 -0000

Blah

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

chriswpage — Mon, 07 Jun 2010 11:39:53 -0000

I wouldn't necessarily say memcache is outdated either, but you do have to use it the way it was intended to avoid those headaches.

For point 2, "good vs bad" design is relative to the scaling requirement.

In any case, point 3 handles the single key approach to scale the cache to millions of product ratings.

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

mrkris — Mon, 07 Jun 2010 01:45:18 -0000

It's poor design to have a hash store all the ratings. A single key is fantastic, the issue is that memcache is outdated. Just my honest opinion.

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

chriswpage — Sun, 06 Jun 2010 22:50:24 -0000

Well, one point here is, you mention that you are caching in the view state, but the example of what you are caching is straight from the data layer. I would first consider handling the cache logic for data closer to the data layer, far from the view.

Secondly, since this appears to be a manual expire, for this particular example, what you are caching ( using memcache ) may be too specific to be doing such a manual expire. Unless you have literally millions of products in the same memcache instance, you gain very little by caching each star rating in it's own key/val. An alternative is to use one key, and put all the star ratings in a data structure under that key - or the if the value size limit is an issue, know your data, and create a handful of known key names to meet that limitation. That way the manual expire can be easily controlled.

Thirdly, if this is not a manual expire, consider a key name convention that matches the value. Ie, if this is a star rating for product a product, incorporate the product SKU onto the key name. Ie:

KEY="rating_NIN-WII-BLACK-00001-OEM "
VALUE="5"

The 3rd point makes manual cache and automated cache simple and is more "memcachey".

So final point, if you choose to use memcache, implement it in a more "memcachey" way to save a lot of headache.

Not a sermon, just a thought.

www.chriswpage.com

Re: Authlogic and rescue_from ActionController::RoutingError

Will Jessop — Mon, 31 May 2010 17:23:27 -0000

Thanks for sharing the fix!

Re: Authlogic and rescue_from ActionController::RoutingError

thermistor — Fri, 28 May 2010 23:42:13 -0000

+1 this fixed it for me, thanks.

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

mrkris — Tue, 18 May 2010 11:48:32 -0000

I've since moved to Redis for caching. It's solved virtually all my problems related to caching.

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

Footstrapping — Tue, 18 May 2010 11:44:04 -0000

Here's what I do when I MUST manage expiration manually. Which is the minority of the time.
1. come up with a scheme for tracking keys. For instance, I might generate a tracking key named "#{user.login}---movies"
2. cache an array indexed by the tracking key.
3. any time you cache data relating to a user's movies, add the key to the list of keys stored under "#{user.id}---movies". When you need to expire those keys, get the list using the tracking key, and delete everything on the list.
-----
The problem is now you are performing many calls to memcached, and a really expensive call to the database might still be cheaper.
Anybody got any better ideas?

Re: Paperclip before_process For Your Habitual Pornographic Needs

airy — Tue, 11 May 2010 17:39:08 -0000

Great!

thanks

Re: Authlogic and rescue_from ActionController::RoutingError

Nathan Colgate — Thu, 18 Mar 2010 14:30:57 -0000

Just what I needed. Thanks

Re: Affiliate Click Tracking With Rack And Redis Because I Care

Adam — Tue, 26 Jan 2010 01:27:18 -0000

Would love to hear more about the analytics you're running against the data collected in redis. Thanks!

Re: Affiliate Click Tracking With Rack And Redis Because I Care

mrkris — Thu, 26 Nov 2009 16:33:34 -0000

In the system I'm building, you just add more nodes to post-process the clicks, unlike most click tracking systems that process on click then redirect.

Re: Affiliate Click Tracking With Rack And Redis Because I Care

BenDamond — Thu, 26 Nov 2009 16:18:56 -0000

Hi! great idea, interesting method but I guess it is a lot to work to create click tracking to work very good, although I appreaciate that you decided to post your work not everybody does that.

______________________
Affiliates

Re: Authlogic and rescue_from ActionController::RoutingError

jbasdf — Fri, 13 Nov 2009 18:00:44 -0000

For what it's worth I had to do the same thing in my rescue method. I was worried that it was a bit of a hack, but now that I see others doing it I feel like it's the right thing to do :-). Thanks for the post.

Re: If You Cant Learn For Yourself Go Back To PHP

Tyron — Wed, 04 Nov 2009 08:54:17 -0000

Actually... I learned a lot by reply to "stupid" questions made by lazy people, and found by google obviously... and I'm still doing it...
Maybe that those lazy people (or casual programmers) will never become competitive in the rails world, but nonetheless they are quite useful, particularly avoiding me fools...

Re: If You Cant Learn For Yourself Go Back To PHP

Carl Fyffe — Fri, 30 Oct 2009 17:26:19 -0000

A great place for these types of questions is http://stackoverflow.com Good questions will be answered and add to the corpus of knowledge that is StackOverflow. Also, if the question has already been asked, there is a good chance that StackOverflow will tell the writer about it and save them some time.

Re: Affiliate Click Tracking With Rack And Redis Because I Care

Andrea Pavoni (apeacox) — Thu, 29 Oct 2009 17:43:23 -0000

I agree with you :) but the app had to be very similar to analitycs. the goal was to sell/buy banners from/to affiliated sites. so we had to calc collected data in way to give a value for ads. moreover, we had only that tools, I'd use other ways and/or technologies :P
anyway, your solution looks very interesting! getting request and repliyng with a redirect is a cool idea (and redis too) ;-)

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

mrkris — Thu, 29 Oct 2009 13:41:20 -0000

Will look into this, thanks!

Re: Why MemCache Makes Me Want To Spoon Out My Own Eyes

Jauder Ho — Thu, 29 Oct 2009 13:28:37 -0000

Have you seen the post by Tobias (from Shopify)? Essentially, he advocates versioning the fragments and letting the older fragments fall out of memcache.

See http://blog.leetsoft.com/20...

Re: Affiliate Click Tracking With Rack And Redis Because I Care

mrkris — Thu, 29 Oct 2009 12:18:47 -0000

Interesting method, though I don't think it's easily maintainable. I only say this because placing JS on each page to track it seems overkill. The way I have it working is you hit the click tracking system and it redirects you. Track from one point for clicks, track per page with analytics for site specific tracking.

Re: Affiliate Click Tracking With Rack And Redis Because I Care

zaach — Thu, 29 Oct 2009 08:23:50 -0000

Oh, yeah, that makes more sense.

Re: Affiliate Click Tracking With Rack And Redis Because I Care

Andrea Pavoni (apeacox) — Thu, 29 Oct 2009 08:20:03 -0000

hi mrkris,

to implement link tracking, I've used a LAMP stack (lack of choice from customer). the tracking worked in a way similar to google-analytics:
- in the affiliate page, insert a reference to a remote js, specifying ID of the site (yes, generate a custom JS for each request related to an affiliate site). the js can eventually load an image (for example a banner) working on the page DOM (that's why there's a custom generated JS).
- the system gets the requests and save the record. if there's a cookie, then check the record on db for eventual UPDATES instead of INSERT (speacking in SQL terms). saved referer too.
- every 10-15 secs, the JS make ajax update request, so there's a track of time per page.

I've worked on the analisys and first core implementation of that system (http://bit.ly/1c1Pk1), then I left the job to others (I was a consultant) . I know it isn't the best way of doing link tracking, but it worked very well :) (seems that the official launch will be during the next weeks).

if you want, we can talk about it more in detail ;)

cheers,
apeacox

Re: Affiliate Click Tracking With Rack And Redis Because I Care

mrkris — Thu, 29 Oct 2009 01:19:14 -0000

I was more meaning, Rack on Rails -- With Sinatra, `ab' was yielding between 700~ requests/sec, whereas Rails is yielding 350~ requests/sec.

Re: Affiliate Click Tracking With Rack And Redis Because I Care

zaach — Thu, 29 Oct 2009 00:56:23 -0000

Sinatra runs on Rack, so I'm not sure how Rack could be slower. Rails also runs on Rack, so you could conceivably use this middleware with either framework, or a minimal Rack app as I believe you suggest.

Re: Making Money While Pooping

Dom — Fri, 16 Oct 2009 23:57:31 -0000

I was so afraid that this entry was going to include something like "Items needed: (1) Webcam" ... glad it didn't. Good advice. ;-)