this post was submitted on 05 Jan 2024
16 points (100.0% liked)

Programming

17402 readers
110 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
16
This benchmark seems irrelevant (devclass.com)
submitted 10 months ago by RealBot@lemmy.world to c/programming@programming.dev
6 comments fedilink hide all child comments
 

The benchmark with 1B rows in this blogpost seems irrelevant for comparing performance of different programming languages.

It seems like the execution time of a program would be dominated by loading data from the file. And a lot of people posted solution with specs of cpu but not specs of disk (hdd, ssd, raid) although that seems more relevant.

Why would they compare languages and solutions in this way?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] aubeynarf@lemmynsfw.com 13 points 10 months ago (1 children)

For most organizations, the cost of paying programmers far exceeds the cost of CPU time; benchmarks really should include how long the solution took to envision/implement and how many follow up commits were required to tune it.

[โ€“] aluminium@lemmy.world 3 points 10 months ago* (last edited 10 months ago)

Also big "enterprise" Software usually becomes slow due to fundamental issues or issues in the architecture.

For example I worked on maintaining an old Java EE project and people there constantly made multiple sequencial HTTP requests despite the requests not being dependent on one another.