Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by stuartaxelowen on Thursday March 31, 2016 @07:57PM
(#11401524)
That is definitely false - single core performance still matters a lot in many ML applications, where utilizing many (>8) cores is still difficult.
[ Parent
| on HN ]
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by jakub_h on Thursday March 31, 2016 @08:25PM
(#11401666)
If by ML, you mean machine learning (and not, e.g., Ocaml et al.), I thought those people were actually into GPUs.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by stuartaxelowen on Friday April 01, 2016 @10:55AM
(#11405195)
GPUs are useful for deep learning and a few other easily parallelizable algos, but the majority of open source ML software is still stuck in the CPU.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by ChrisDutrow on Thursday March 31, 2016 @11:46PM
(#11402427)
Redis is mostly single thread.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by astrodust on Friday April 01, 2016 @01:43AM
(#11402911)
This is not really a great thing about Redis.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by ChrisDutrow on Friday April 01, 2016 @02:13PM
(#11407132)
It would be a more powerful tool if it was multi-threaded. I'm not an expert, but my impression that it was able to be more powerful in other ways (stability, features) because of the choice to make it mostly single threaded (given labor and complexity constraints).
Is there an alternative RAM database that you like better that is multi-threaded?
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand...
by astrodust on Saturday April 02, 2016 @10:06PM
(#11414589)
As much as Redis is an incredibly potent tool and the quality of craftsmanship on it is very high, there are some incredibly peculiar design decisions that have been made.
Single-treading is one of those. There are times when having more than one thread to help process things would come in very handy, though I recognize that the cost of adding this can be very high.
It's something that will have to be addressed eventually for a single Redis process to take advantage of newer hardware with very low ceilings on CPU power, but huge numbers of cores.