blaforge

4 ms·

1. 1.▲
   by blaforge 14y ago

   I had only 2 years of experience with Scala and was not always able to foresee the overhead of various language constructs. As this was my first project where I considered performance critical, I decided to stick with Java--with which I hav
2. 2.▲
   by blaforge 14y ago

   I'll admit it, the disruptor architecture was my inspiration. I've since put together an in-memory database built on JActor that processes a million ACID transactions a second (on an i7 with ssd). https://github.com/laforge49/JFile What I
3. 3.▲
   High throughput Java actors--much faster than Akka

   5 points by blaforge 14y ago|4 comments
4. 4.▲
   by blaforge 14y ago

   For another perspective, you should take a look at JActor. https://github.com/laforge49/JActor JActor is a high-throughput JAva actor framework capable of delivering up to 200 million messages per second on an i7. It achieves this by oper
5. 5.▲
   by blaforge 14y ago

   Take a look at JActor, a high-throughput Java actor framework. It gains its speed by operating mostly synchronously and delivers between 80 and 200 million messages per second, depending on the mode of delivery. https://github.com/laforge4
6. 6.▲
   by blaforge 14y ago

   Exceptions can be quite problematic. This is why JActor has taken such pains in its exception handler. One particularly nice feature is that, since JActor supports 2-way messages, the default exception handler passes exceptions to the activ