this post was submitted on 02 May 2025
19 points (100.0% liked)

Programming

20237 readers
501 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 [email protected]



founded 2 years ago
MODERATORS
19
database greenhorn (discuss.tchncs.de)
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]
 

hi my dears, I have an issue at work where we have to work with millions (150 mln~) of product data points. We are using SQL server because it was inhouse available for development. however using various tables growing beyond 10 mln the server becomes quite slow and waiting/buffer time becomes >7000ms/sec. which is tearing our complete setup of various microservices who read, write and delete from the tables continuously down. All the stackoverflow answers lead to - its complex. read a 2000 page book.

the thing is. my queries are not that complex. they simply go through the whole table to identify any duplicates which are not further processed then, because the processing takes time (which we thought would be the bottleneck). but the time savings to not process duplicates seems now probably less than that it takes to compare batches with the SQL table. the other culprit is that our server runs on a HDD which is with 150mb read and write per second probably on its edge.

the question is. is there a wizard move to bypass any of my restriction or is a change in the setup and algorithm inevitable?

edit: I know that my questions seems broad. but as I am new to database architecture I welcome any input and discussion since the topic itself is a lifetime know-how by itself. thanks for every feedbach.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 9 hours ago (1 children)

Realistically, this setup is 10 years too old

thanks for this input. This was the winning argument for my boss for migrating to a modern server. While I admit that I see many flaws in our design, we are now working on refactoring our architecture and approach itself.

Thanks to the other numerous answers leading me to the right direction (hopefully).

[–] [email protected] 1 points 7 hours ago (1 children)

This was the winning argument for my boss for migrating to a modern server.

Exceptionally good news! Glad it's working out. Be sure to make a new post when you decide what you go with, I'm sure people here would enjoy hearing about your approach.

[–] [email protected] 1 points 7 hours ago

Well. For now the system is not yet running on the new hardware.

It is now a pondering process of whether migrating everything as it is to the new hardware and then optimize/refactor.

Or refactor before (or at least develop a plan) and then improve during migration....

Be sure to make a new post when you decide what you go with, I’m sure people here would enjoy hearing about your approach.

Nice to hear. Thanks. I will share updates.