sorenso

8 ms·

31.
by sorenso 12y ago
I'm not sure I understand your concerns. Can you please elaborate?
32.
by sorenso 12y ago
Thanks for your reply! I know, but this is still a common way of making objects. I've seen it several times, but I don't like it ;) -sorenso-
33.
by sorenso 12y ago
Because it's the foundation of all modules and if you start of on the wrong path it can only get worse. On a daily basis I'm working on web applications with more than 5000 req/sec, so it's important to make sure your co
34.
by sorenso 12y ago
Thanks for your comment! I've checked and console.log is not there in the code I ran in my benchmark. I re-ran the tests right now to make sure I didn't screw up this. Best regards, -sorenso-
35.
Node.js module performance(litt.no)
46 points by sorenso 12y ago|21 comments
36.
by sorenso 12y ago
Thank you for your comment! Please do a write up on your experience. I'll be happy to read about it. Best regards, -sorenso-
37.
by sorenso 12y ago
Hi mbell, Thanks for commenting! What kind of application are you using with the SQS (language, purpose, usage)? It would be interesting to know for me :) This test was only running for 50 minutes, maybe this could be the issue? Best regard
38.
by sorenso 12y ago
Thanks for commenting! What is your traffic rate in request pr second? I would be interesting to know. SQS is a simple and easy to use service. I really like it, but as you read in my post. I'm a bit concerned about the scaling. We are
39.
by sorenso 12y ago
Thanks for commenting! I'll be happy to answer any question about my implementation and testing. In this test I'm using a standard SQS service i region EU-west. My integration with SQS is done from a simple application written in
40.
A performance test of SQS(litt.no)
12 points by sorenso 12y ago|9 comments
41.
What I've learned working with Amazon SQS(litt.no)
2 points by sorenso 12y ago|0 comments
42.
Amazon ELB latency problems(litt.no)
3 points by sorenso 12y ago|0 comments