group by / distinct mysql vs javascript filter performance

Question

Say I have a many to many relationship and when I query the db for the left table using a join from the right table I get duplicates because of this many to many relationship. I can use group by on the primary key to get rid of these in mysql or distinct.

However I've been told that distinct & group by are not good re:performance. With that said, I would also assume mysql performance would be better than javascript performance.

Should I be filtering my results in javascript or use group by in mysql? Any reason why one would be faster than the other?

As pointed by @Rushed this largery depends on the scenario you are facing. Generally speaking when i face many-to-many relations i always try to implement a third table of relations in order to avoid complications with distinct/group by... — holden
– holden, Commented Oct 26, 2017 at 20:46

Rashed Addosary · Accepted Answer · 2017-10-26 20:14:30Z

1

it depends on how much data and how many concurrent users:

if the data is reasonably low and not much concurrent users then mysql group by/distinct is the best solution.
if the data is reasonably low and high concurrent users then Javascript filtering is the best solution here.
if the data is large regardless of how many concurrent users then you should look for another solution than just group by/distinct and I'm not talking about filtering in javascript because in this case the huge data will cause low performance in user's browser.

answered Oct 26, 2017 at 20:14

Rashed Addosary

717 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

group by / distinct mysql vs javascript filter performance

1 Answer 1

it depends on how much data and how many concurrent users:

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

it depends on how much data and how many concurrent users:

Comments

Your Answer

Sign up or log in

Post as a guest

Related