a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment by user92
user92  ·  4147 days ago  ·  link  ·    ·  parent  ·  post: Hubski PSA: You killed Hubski!

Have you thought about load balancing across one or more nodes? You're going to have to at some point.





akkartik  ·  4147 days ago  ·  link  ·  

Haha, more than one node. That's pretty non-trivial for the way hubski is currently built: https://news.ycombinator.com/item?id=5032739

(Notice that pg corrected my more general comment, but making the changes he suggests to hubski is still non-trivial.)

Update: you'll probably want to read the original story first, the programmer types among you: http://davidkendal.net/articles/2011/11/a-man-a-plan

rozap  ·  4142 days ago  ·  link  ·  

So the issue is that the fnid links reference a function's closure, which is stored in a hashmap? So the more fnid links get served up, the more memory gets used? And then when it expires, you get the unknown or expired link sort of thing?

Sounds like this wouldn't translate very well into multiple machines, unless figured out a way to store closures externally.

akkartik  ·  4142 days ago  ·  link  ·  

Yup, yup, yup and yup :)

rozap  ·  4142 days ago  ·  link  ·  

Ouch. Do you guys have a plan in place for dealing with this?

akkartik  ·  4142 days ago  ·  link  ·  

Yeah it's not insurmountable.

rozap  ·  4142 days ago  ·  link  ·  

Awesome.

user92  ·  4147 days ago  ·  link  ·  

It also makes it sound like running behind a CDN (or any kind of proxy) won't work too well. That really sucks. I don't care too much for programming language pissing contests, but if that's really a limitation, well...that's a pretty severe one to say the least.

lelandbatey  ·  4146 days ago  ·  link  ·  

I'm not sure it is a programming language limitation. The link in the link above points out the Paul Gram pretty much pioneered lisp on the Web, and that most thing just emulate his ideas. That means that change could come, but that right now the "standard" implementation has limits. This is good, but requires a lot of work to make happen.

rozap  ·  4146 days ago  ·  link  ·  

I agree. It does sound like a major issue.

@mk, thoughts on the above articles?

rozap  ·  4147 days ago  ·  link  ·  

Also caching all the things. I'm not sure how arc would integrate with memcached though, for after some googling, it doesn't appear to have any bindings already written. Not surprising due to the tiny adoption of it. For a short term bandage, varnish doesn't really care what's upstream of it, I believe.

Unfortunately, there are some serious issues that come from adopting an un-adopted language. And I think that's why reddit moved to python. Not saying it won't work, just saying it's a lot more work to make it work. It's certainly important for people to experiment with less widely used languages - that's how movements are formed.

user92  ·  4147 days ago  ·  link  ·  

Yeah. I've found the cheapest and easiest quick fix is to setup with Cloud Flare. Their free tier is still a pretty good CDN offering.

rozap  ·  4147 days ago  ·  link  ·  

Good point, I've heard nice things about them. For mk's sanity's sake, I hope a change in toolsets isn't required. That would be a big effort.

user92  ·  4147 days ago  ·  link  ·  

Yeah that's why things like Varnish (which still required work and $) and Cloud Flare (which is stupid simple to setup) are so good because they are generally back-end agnostic.

rozap  ·  4147 days ago  ·  link  ·  

Hm, why would varnish require money? Unless you're going by the fact that time = money. It is open source...

user92  ·  4147 days ago  ·  link  ·  

In that you need to buy/rent the servers to install it on.