pfalls

7 ms·

31.
by pfalls 14y ago
One of the next steps we'd like to take is to have a test that does cover a more typical web request, and is less database heavy than our 20 query test, just like you describe. Ultimately, we felt that these tests were a sufficient starting
32.
by pfalls 14y ago
We wanted to use an ORM in all cases, it was only recently that we started working on native mysql access. We hope to add native mongodb results as well.
33.
by pfalls 14y ago
This is great to know, we were hesitant to use non-stable versions (although we were forced to in certain cases), but knowing that it's what is common practice for production environments would change our minds.
34.
by pfalls 14y ago
EC2 was a hard platform to test on, only because our i7 hardware would give us results fairly instantaneously, but we became impatient when we had to wait upwards of 10x as long for the data on the EC2 large instances. We're actually very i
35.
by pfalls 14y ago
I think you're about right on that one. Of course we were running on mono.
36.
by pfalls 14y ago
Thanks for the comment! This started out as a small exercise, that quickly ballooned because we were curious about every framework and platform. Obviously we had to stop somewhere, but we're very interested in adding more tests in the futur
37.
by pfalls 14y ago
We attempted to take advantage of threading/multiple-processes as best we could (see the nodejs code for an example of using the cluster module). But we suspect there are additional areas of improvement here.
38.
Web Framework Benchmarks(techempower.com)
438 points by pfalls 14y ago|396 comments
39.
by pfalls 14y ago
All I ever heard about with Java 8 was lambdas (which is understandably the big name new feature), but streams, in my opinion, are just as exciting. Unlike lambdas and they're new syntax, streams seem like something any developer can quickl
40.
by pfalls 14y ago
Streams, lambdas and the new time API are wonderful additions to Java.