To avoid completely saturating the server.
Right now we advise using s3 and storing results in files, and asynchronously loading them with batch processes.
361 karma · joined January 3, 2022
To avoid completely saturating the server.
Right now we advise using s3 and storing results in files, and asynchronously loading them with batch processes.
PostgreSQL has historically been bad at managing the noisy neighbor problem, but with thread pools, and io priorities, it can be solved.
Has this been tackled here ?
One would be able to trigger maintenance jobs via simple lambda functions whose duration is capped.
Has anybody seriously benchmarked this ?
I don’t think io uring would make a difference with this setting but I’m curious, as it’s the default for oracle and sybase.
I know other people in the kernel do the same mistake as you frequently do on mailing lists. But two wrongs do not make a right.
This way you wouldn’t be so preoccupied about getting code as fast as possible in the kernel.
In any case as a Linux user, I want to thank you for your work and for your code which taught me a lot.
I hope it didn’t take too much of a toll on you.
Let’s hope that with the recent stabilization, the maintenance will be easier.
And Mr Overstreet’s behavior is still unprofessional.
I think this thread is really insightful to teach highly skilled individuals that people skills are as important as technical proficiency.
I have been this arrogant and abrasive dev. It’s bad and learning how to behave, mainly through parenting, was a net positive for my career.
People, please read and learn from this thread.
I do not live in the US but did see some truly shocking and illegal behaviors at gay prides and drag themed events.
So I’m just waiting to get more information.
So my point is to trust the law. I don’t see how controversial it can be.
And performant enough.
Engineers ship with them, and do not care if there’s a purer system elsewhere.
The new design makes the event loop / io much easier to reason about. Thanks Andy
Regarding crypto operations, I know as of now for rust projects assembly is a must to have constant time guarantees.
Maybe there could be a way with intrinsics and a constant-time marker, similar to unsafe, to use pure rust.
In the meantime I think there still is too much C code.
It’s a great step in the good direction by the way.
I think it’s not a good indication of the success of the language.
Good to know a totally offline tool is being considered.
Thanks for the great tool BTW.
I think people should be aware that the Core Storage work is not beeing done in the open anymore. The process of letting the open source core grow useless while selling proprietary addons is fine. I just have a problem with people calling this open source.
Some prefer using open source. Are they leeches ?
Regarding scaling open source projects, did Linux scale ?