GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

until_the_cores_are_all_saturated_there_is_no_use_having_more_of_them.png

Download link

https://freespeechextremist.com/media/73bcd2e3-7b3f-459e-9d12-5d2ad9168f0a/until_the_cores_are_all_saturated_there_is_no_use_having_more_of_them.png?name=until_the_cores_are_all_saturated_there_is_no_use_having_more_of_them.png

Notices where this attachment appears

  1. Embed this notice
    pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Sunday, 14-Jan-2024 23:00:02 JST pistolero :thispersondoesnotexist: pistolero :thispersondoesnotexist:
    in reply to
    @i @dcc @p

    > why tho,

    Contention for the memory bus is the biggest performance hit on $current_year CPUs and aside from that, the biggest performance bottlenecks for Pleroma are, in order, disk I/O and network I/O. The CPUs on the box mostly sit idle, meaning that more hardware threads wouldn't accomplish anything but heating the machine up.

    I suspect that it's faster with less NUMA-wrangling, but have not benchmarked it. I just know that on this workload, I could probably disable half the physical cores and still have no trouble.

    > plan9'tism?

    I don't know what that'd have to do with a hardware feature on a machine that runs Linux and a handful of VMs.
    until_the_cores_are_all_saturated_there_is_no_use_having_more_of_them.png
    In conversation Sunday, 14-Jan-2024 23:00:02 JST from freespeechextremist.com permalink
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.