Sharing page tables with msharefs
Sharing page tables with msharefs
Posted Jul 15, 2022 14:32 UTC (Fri) by clugstj (subscriber, #4020)Parent article: Sharing page tables with msharefs
Posted Jul 15, 2022 14:38 UTC (Fri)
by willy (subscriber, #9762)
[Link] (11 responses)
Posted Jul 15, 2022 15:28 UTC (Fri)
by clugstj (subscriber, #4020)
[Link] (7 responses)
Posted Jul 15, 2022 17:11 UTC (Fri)
by malmedal (subscriber, #56172)
[Link] (2 responses)
Posted Jul 15, 2022 18:11 UTC (Fri)
by k8to (guest, #15413)
[Link] (1 responses)
(Sort of a joke, because no one should be. But sort of true because they tend only win in the case of very fragile tuning that cannot be done in a timely way. And because of course if you spent that same money on hardware, you'd usually be better off with postgresql.)
Posted Jul 15, 2022 20:20 UTC (Fri)
by malmedal (subscriber, #56172)
[Link]
Several years out of the loop now, but I remember that Oracle, at least used to be, up to twice as fast as
Posted Jul 16, 2022 6:20 UTC (Sat)
by mokki (subscriber, #33200)
[Link] (3 responses)
I was under the impression that thread per client model is faster, but less safe. In process per client model a bug in one client cannot corrupt memory in the process, outside the explicitly shared memory area.
Posted Jul 16, 2022 9:44 UTC (Sat)
by edeloget (subscriber, #88392)
[Link] (2 responses)
Yes, but then, correct system architecture tells you to limit the number of clients to something that the machine can handle :)
If you cannot have 1500 clients on a signe machine, then maybe you shouldn't have 1500 clients on the same machine :)
Posted Jul 16, 2022 9:58 UTC (Sat)
by flussence (guest, #85566)
[Link] (1 responses)
Posted Jul 16, 2022 18:32 UTC (Sat)
by butlerm (subscriber, #13312)
[Link]
Posted Jul 15, 2022 19:55 UTC (Fri)
by josh (subscriber, #17465)
[Link] (2 responses)
Posted Jul 15, 2022 20:52 UTC (Fri)
by bartoc (guest, #124262)
[Link]
Posted Jul 15, 2022 22:59 UTC (Fri)
by nickodell (subscriber, #125165)
[Link]
> That raises an obvious question, he said: why not just use threads? The answer was that "mmap_lock sucks". It is also not possible to change the existing behavior of MAP_SHARED, since that would break programs, so there would need to be, at a minimum, a new mmap() flag if not a new system call. Aziz said that the separate system call makes the page-table sharing explicit rather than it just being a side effect. That makes the decision to opt into this behavior explicit as well.
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
PostgreSQL and MySQL on the same hardware and also the Magic Money Tree would provide far more money for
Oracle hardware since the license was so expensive :(
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs
Sharing page tables with msharefs