Re: Ultimately, speed will increase further in Computing in Memory(CIM)
That's all well and good, but the fact that memory access is so slow is a problem for writing efficient code.
Yesterday I was discussing implementing a large data set as a linked list so it would be very efficient to break off chunks of it and move them to over objects. He point out that the disadvantages of memory fragmentation were so significant (largely because the data won't be loaded into cache together) that it was usually better to just put the data in an array and accept the cost of copying things when it happens.
Yes there is alot of inefficient gibberish in the world (interpreted languages still exist), but even when you are trying; the unbalanced nature of modern hardware performance heavily favors some practices that should logically be slower.
Biting the hand that feeds IT
