Viewing profile — purplefox

Very excited to announce the release of a new open source project Tektite. Tektite allows you to create topics (like Kafka or RedPanda) but also do processing (like Flink) and lots…

I haven't looked at this detail yet, but it should be noted that we haven't even optimised Vert.x yet so there should be plenty of scope for further improvement :) (Disclaimer: I'm…

The JVM does not doing any caching. And artificially crippling Vert.x to a single core does not prove anything. Anybody who cares about performance will be using more than one core…

I've tested several combinations of blocking, non blocking, readFile, streams (pipe) and using chunked transfer encoding. Results vary a little but all way below the Vert.x results…

People have already got Vert.x running on OpenShift and Heroku, and CloudFoundry support shouldn't be too much longer.

Hopefully Scala won't be too long :)

+1. The system is in steady state, i.e. queues of requests/responses aren't growing. Therefore it doesn't actually matter if you count the requests or the responses.

The flaw in your argument is that the server is spending 80% of its time reading a file from disk. It's more than likely that it spends close to 0% of its time in disk access since…

Vert.x has a hybrid model. It has both event loops and a background thread pool, so you can choose which to run your task on depending on what kind of thing it is. E.g. it's stupid…

It's labelled badly, what is actually measured is req/resp per second. I.e from request to corresponding response and how many of those it can do per second. If you doubt the numbe…

If you read the docs we specifically mention the "Fibonacci" farce. Vert.x (unlike node) does not force you to do everything on the event loop. It has a hybrid model. For things li…

Agreed, it would be good to have CommonJS support. However, it's unlikely that node modules will work as is with Vert.x, since the API is different. (Unless someone writes a transl…

Yes indeed. You can mix and match Java, JavaScript, Ruby and Groovy in the same app. We hope to support more languages going ahead (e.g. Java, Scala, ...)

http://vertx.io/core_manual_js.html#serving-files-directly-d...

Yes, of course in a real web server you'd make sure you do the checks ;) The documentation actually mentions this point explicitly :)

Yes, I meant threads ;) E.g. A web server using node.js on a 32 core server. You would have to manually manage 32 instances of node, and use a load balancer or the cluster module i…

If the wire protocol for the driver is published, then you can write a 100% async driver for it. I.e. no threads blocking, ever. In fact, I already did this for redis and vert.x (I…

Yes, vert.x should work directly on Windows. I shall update the wiki accordingly :)

Fibers (or equivalent constructs) aren't supported by all the languages that Vert.x supports (e.g. Java) so we can't really support something like that until we can do it in all th…

That's right. If you use the sendFile() method and you're on an OS that supports it, then the kernel will do the copying directly from file to socket for you. You can also serve fi…