pinaraf

5 ms·

1.
PostgreSQL copy-patch JIT, episode III(pinaraf.info)
2 points by pinaraf 10mo ago|0 comments
2.
by pinaraf 11mo ago
And the latest driver available for Jetson Thor doesn't have the fixes for these two CVEs because they decided to fork their own driver...
3.
JIT: So you want to be faster than an interpreter on modern CPUs(pinaraf.info)
170 points by pinaraf 11mo ago|63 comments
4.
by pinaraf 3y ago
The real difference is in the possible optimizations. If you consider the full scope of JIT compilation in for instance a web browser or the JVM, you could use copy and patch as a tier 0 compiler, and once really hot paths are identified, t
5.
by pinaraf 3y ago
Yeah, well, sorry, I should have been more explicit here: the issue is with PostgreSQL, not LLVM. The JIT compiler has to inject direct memory addresses, making the generated code specific to your query and process.
6.
by pinaraf 3y ago
Same for me, that's why I did this after finding out this research paper. With the proper compiler settings and small tricks you can remove some parts and already end up faster than the interpreter (because you remove some branches and
7.
by pinaraf 3y ago
Indeed, and right now it's the only possible way since it remains in a single session, doing otherwise would be very hard.
8.
by pinaraf 3y ago
Honestly I thought the same as you, then I wrote this, and I now understand it's going to be really hard to do. To make it very simple: there are pointers to query parts "leaking" everywhere across the execution engine. Remov
9.
by pinaraf 3y ago
Two parts: I did the benchmark on a laptop and didn't spend enough time forcing its runtime PM in a fixed state, I'll run a real pgbench on my desktop once I implement all required opcodes for it. And since JIT requires a minimum
10.
by pinaraf 3y ago
Author here. Thanks for submitting my article on hackernews. I'll do my best to answer any question.
11.
PostgreSQL – Using Row Level Security with a Django Application(pinaraf.info)
2 points by pinaraf 9y ago|0 comments
12.
by pinaraf 10y ago
PostgreSQL streaming : send disk diffs over network, raw binary, absolutely unusable if you don't have the same postgresql version on the other side Logical : send data diffs over network. Could be used for replication, but also audit
13.
by pinaraf 10y ago
Static checking ? Python 3.5 Asyncio ? Python 3.4 If these had been available in Python 3.2 or even better 3.0, the switch would have been far easier for corporate users that need benefits before accepting the cost of change...
14.
by pinaraf 10y ago
Well, it weights in favor of Python 2, and considering that until recently the incencitives for Python 3 were still light... It's not really about having users, but having the possibility of switching from CPython to PyPy if you face p
15.
by pinaraf 10y ago
So much work where there are many other solutions out there that don't have that limitation : PostgreSQL, several NoSQL databases...
16.
by pinaraf 11y ago
Debian sid, what else... On desktop, laptop, servers... Tools : QtCreator / KDevelop for C++, Netbeans for Java, vim or Kate for everything else