Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

icky -- don't know if you know it or not, but Paul's writing his own application language, Arc, and testing it out on this board.

To my knowledge he is not using an Apache stack. In addition, he's doing a keyed-continuations deal across loads/posts, so he's effectively keeping the stack around for each user.

Really cool stuff, but I can see where memory can become an issue. He's probably running into paging issues and trying this out as a fix.

At least I think that is the situation.



> icky -- don't know if you know it or not, but Paul's writing his own application language, Arc, and testing it out on this board.

"Whoa, you mean this isn't wood shop class?" ;-)

> To my knowledge he is not using an Apache stack.

For static pages, there's no reason he can't stick an Apache in front.

> In addition, he's doing a keyed-continuations deal across loads/posts, so he's effectively keeping the stack around for each user.

That part might be tricky to optimize, but there ought to be a way, even then, to avoid hitting the app server for static page loads.

Edit: Looking at the login cookie across page loads, it's just a session-id. There is absolutely no reason that the app server ever need know about these cached static page loads.

> Really cool stuff, but I can see where memory can become an issue. He's probably running into paging issues and trying this out as a fix.

He's also running into state issues, since he's keeping all session state as in-memory continuations, which is probably forcing him to keep news.yc on one box.

One thing that might work is to come up with a way to serialize those continuations, and store the key-value pairs in a memcached box. Then the app server can become stateless again, and he can add more boxes.


> For static pages, there's no reason he can't stick an Apache in front.

For static pages, there no reason to stick Apache in front.


> For static pages, there no reason to stick Apache in front.

Are you suggesting that static pages should hit the app server?


No I'm suggesting that static content be served by something lighter than Apache.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: