2,635 karma · joined August 26, 2008
The communists had a solution.
At the downtime I felt like +20 or 30 years older and gone retarded. Can't do any more hard brain work, and felt like I can't do that ever.
But this will pass.
HTTP with connection: keep-open can serve 100k req/sec. But that's for one client being served repeatedly over 1 connection. And this is the inflated number that's published in webserver benchmark tests.
For more practical down to earth test, you need to measure performance w/o keep-alive. Request per second will drop to 12k / sec then.
And that's for HTTP without encryption or ssl handshake. Use HTTPS and watch it fall down to only 400 req / sec under load test [ without connection: keep-alive ].
That's what I observer.
https://www.mit.edu/~yandros/doc/specs/fcgi-spec.html
Easier than integrating a 3rd party tool.
I regularly compile a lot of stuff on this machine, indicating I never needed that before.
So none of the software I compiled had 32 bit time_t. And we still have 15 more years to migrate anything remaining behind.
#include <time.h>
#include <stdio.h>
int main(){
printf("%d\n",sizeof(time_t));
}
$ gcc -o time time.c
$ ./time
$ 8
Therefore time_t is 8 bytes at least on 64 bit systems, even when you are using default time_t and not time64_t.No idea when it was changed. 20 years back?
printf("%d\n",sizeof(time_t));
outputs : 8
////
Are compilation times a problem with Rust? Yes.
Are build times as bad with Rust as with C++? Yes.
Looking at my hypotheses, I was wrong on all counts:
The Rust port had more lines than the C++ version, not fewer.
For full builds, compared to Rust, C++ builds took about the same amount of time (17k SLOC) or took less time (100k+ SLOC), not longer.
For incremental builds, compared to C++, Rust builds were sometimes shorter and sometimes longer (17k SLOC) or much longer (100k+ SLOC), not always longer.
Now 25 years later, watch what's actually made the most money, and did his reply cover those. I can think of hosted services and search.
Even Microsoft had one of the very first maps online in the 90s [ terraserver ] but they failed to realize how large this business eventually will turn into.
I was worried whether their core developers were unionizing or not.
Not yet. Not even the game developers.
Here are my use cases of a SQL parser at application level.
- enumerate, add, delete conditions from WHERE clause.
- change ORDER BY.
- paging, LIMIT.
- turn an aggregate query into crosstab query.or maybe run redundant monolith fail over servers. should work the same as micro services.
At least not as unfair as I initially thought.