That hasn't been true for more than 8 years now.

Source: https://github.com/rclone/rclone/blob/9abf9d38c0b80094302281...

And the PR adding it: https://github.com/rclone/rclone/pull/2622

* https://www.visa.co.in/about-visa/newsroom/press-releases/vi... * https://pgi.billdesk.com/web/sihub

* https://www.cdnplanet.com/blog/initcwnd-settings-major-cdn-p...

Comments URL: https://news.ycombinator.com/item?id=44291667

Points: 3

# Comments: 0

https://github.com/TryGhost/node-sqlite3/issues/408#issue-57...

https://github.com/WiseLibs/better-sqlite3/issues/32#issueco...

Copying a quote from the second:

> The sqlite3 C API serializes all operations (even reads) within a single process. You can parallelize reads to the database but only by having multiple processes, in which case one process being blocked doesn't affect the other processes anyways. In other words, because sqlite3 serializes everything, doing things asynchronously won't speed up database access within a process. It would only free up time for your app to do other things (like HTTP requests to other servers). Unfortunately, the overhead imposed on sqlite3 to serialize asynchronous operations is quite high, making it disadvantageous 95% of the time.

Comments URL: https://news.ycombinator.com/item?id=42812203

Points: 128

# Comments: 146

> Thruster also wraps the Puma process so that you can use it without managing multiple processes yourself. This is particularly useful when running in a containerized environment, where you typically won't have a process manager available to coordinate the processes. Instead you can use Thruster as your CMD, and it will manage Puma for you.

[1] https://github.com/Lidarr/Lidarr [2] https://github.com/sct/overseerr/pull/3800

From https://www.sqlite.org/pragma.html#pragma_auto_vacuum:

> When the value of auto-vacuum is 2 or "incremental" then the additional information needed to do auto-vacuuming is stored in the database file but auto-vacuuming does not occur automatically at each commit as it does with auto_vacuum=full. In incremental mode, the separate incremental_vacuum pragma must be invoked to cause the auto-vacuum to occur.

Comments URL: https://news.ycombinator.com/item?id=41448985

Points: 492

# Comments: 236

https://hardcover.app/askjules

It requires the music to be already present, however, so not ideal for finding new music.

Intel has a Pretty Big Problem (by Level1Techs): https://www.youtube.com/watch?v=QzHcrbT5D_Y

Intel's CPUs Are Failing, ft. Wendell of Level1 Techs (by Gamers Nexus): https://www.youtube.com/watch?v=oAE4NWoyMZk

Comments URL: https://news.ycombinator.com/item?id=40935449

Points: 8

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=40181377

Points: 3

# Comments: 1

You may want to consider adjusting your partition key (if feasible) as a function of datetime so you can just drop a complete partition when required, rather than needing separate delete queries.

In my experience, it has proven to be a very quick and clean way to clear out older data.