agazso

22 ms·

151.
by agazso 17y ago
You guessed right. Context switching is expensive, and the default stack size default is in the megabyte range. So if you want to have 10K connections open, it takes about 10GB memory. You can of course shrink the stack size, but you have t
152.
by agazso 17y ago
After the industry accepted Java as an enterprise language, lot of development went into optimizing the compiler and these were not academic developments, like your examples (maybe except TraceMonkey). Add this to the already existing huge
153.
by agazso 17y ago
Just an idea: if you add "hacker news" as a keyword, you will get all the articles, and if you add your interests then the articles will be organized as well.
154.
by agazso 17y ago
Reality seems to contradict your opinion. GCC, Linux and thousands of quality libraries are written under GPL license. Releasing software as open source dows not mean giving it away for free. With GPL it literally means that you give it for
155.
by agazso 17y ago
This is what excited me most too. It is a very similar approach than what we did in a project when we had to add multithreading later on, namely to use tasks and hierarchical queues. But with GCD, it has the knowledge of the number of cores
156.
by agazso 17y ago
Thanks, I completely forgot about using shared memory between processes. Lately I used exclusively sockets, as it provides a portable solution between languages and platforms. But you are right, it is not suitable for realtime or low latenc
157.
by agazso 17y ago
I don't get it. At the beginning of the article he talks about the dangers of locking IPC (inter-process communication) calls, then to prevent this, he describes a lock-free mechanism using the CAS primitive, which can be used only in-proce
158.
by agazso 17y ago
And how will CouchDB solve your scalability problems? I am really asking, because there website contains nothing exact about scalability problems. I also tried to read about in the first chapter of the upcoming CouchDB book, but it only con
159.
by agazso 17y ago
The SSL bug in this case happened because the programmers had wrong assumption about the network input (namely it doesn't contain the zero byte value). This type of wrong assumption can be made in any language. And this bug doesn't make buf
160.
by agazso 17y ago
Without being familiar with the details of your use-case, one of the nice properties of Keyspace is that it is a high-performance (async, C/C++, epoll on Linux) UNIX server --- we are able to get 100.000 writes/sec with n=3 replication on f
161.
by agazso 17y ago
Why? Our intention, with the AGPL, versus the GPL is to close the SaaS loophole, so if you base a service on top of a modified Keyspace, you have to publicize your changes. But you can use it, sell it, distribute it, etc. just as you can wi
162.
by agazso 17y ago
While libtask contains primitives for io (see fdread and other fd* functions) it uses poll() internally which does not scale well. And that is one of the problems that libevent solves by using the best available polling mechanism available.
163.
by agazso 17y ago
You seem to completely ignore the fact that there are environments where speed does not matter, but memory is constrained. In those environments even Java is prohibited and C/C++ or even assembly is a way to go, because in these languages y
164.
by agazso 17y ago
What's more, the formal spec doesn't contain important parts, like the connection handshake process. Without that knowledge you cannot make h264 video work.