undefined

points

[-]

My general rule of thumb is that if you see you can 2x it easily, you can actually get somewhere around 10x with effort, since the presence of that easy 2x means nobody really spent any time on performance.

by vrighter5 hours ago|

parent|

[-]

i got over 800 this way. O(n^2) everywhere and n+1 queries

by andyferris34 minutes ago|

parent|

[-]

It can go to extremes. Like 100x by going from a dynamic to static language then 100x more adjusting the data structures/algorithm…

Once I got very confused when exactly this kind of 10k x speed up I demonstrated for a problem introduced to me as a business bottleneck then got ignored (I wasn’t on this team, though, but it’s still hard to understand the mentality and incentives there).

by jonathanlydall4 hours ago|

parent|

prev|

[-]

This sounds like being completely performance oblivious, like an extreme opposite of premature optimisation.

My rule of thumb is that as long as it doesn’t really complicate or convolute the code, write with performance in mind.

My expertise is in C# and sometimes this is as simple as using a hash set or dictionary instead of a plain list.

Other times it’s having a decent understanding of how EF (an ORM) actually works (the static typing benefits of them in C# makes ORMs very valuable when used appropriately) and the cost of round trips to any network host (including a DB).

by vrighter4 hours ago|

parent|

[-]

a hashset was used... then ".Where(x=>x == key).Count() == 0"

by rowanG0777 hours ago|

prev|

[-]

Nitpick but 25% improvement over 8 quarters is 1.25^8, almost a runtime in 1/6th of the time.

by hinkley1 hours ago|

parent|

[-]

25% faster is 1.33x work done in the same time. What you want is 0.75^7 (almost 2 years) gives you 13.3% of the original time, which is 1/7.5. Only it was more like 25-30% so I rounded up.

by kaashif1 hours ago|

parent|

[-]

Interesting how people interpret the word faster differently.

To you, 2x faster means 2x the work done in the same time, but 25% faster means 1.33x the work done in the same time.

I see this a lot - in software people interpret 50% faster as a 50% reduction in time taken.

If a car is 50% faster, I hope people would universally interpret that as e.g. 20 to 30 mph. But if I asked people how long would a 1 hour journey take if it were 50% faster, I bet a lot would say 30 mins, because it kind of seems like that's what I mean.