Group items tagged

Brutalna stranka obsahujuca kopec infogragik, linkov, toolov, slideov ohladom performance monitoring a tuning na Linuxe

vysvetlenie preco nie je velmi vhodne, aby office-management a programatori boli v jednej miestnosti a zvonenie telefonov a postarka vyrusovali tych, ktorych naplnou prace je najma programovat: top performers overwhelmingly worked for companies that gave their workers the most privacy, personal space, control over their physical environments, and freedom from interruption. Sixty-two percent of the best performers said that their workspace was acceptably private, compared to only 19 percent of the worst performers

If you have studied computing science, then you know how to do complexity analysis. You'll know that iterating through a linked list is O(N), binary search is O(log(N)) and a hash table lookup is O(1). What if I told you that all of the above is wrong?

These days it's a pretty bold claim if you say that you invented a sorting algorithm that's 30% faster than state of the art. Unfortunately I have to make a far bolder claim: I wrote a sorting algorithm that's twice as fast as std::sort for many inputs.

New Elastic Volumes Today we are launching a new EBS feature we call Elastic Volumes and making it available for all current-generation EBS volumes attached to current-generation EC2 instances. You can now increase volume size, adjust performance, or change the volume type while the volume is in use. You can continue to use your application while the change takes effect.

Matz is experimenting with three concepts that may or may not be included in Ruby 3.0. 1. Man-machine collaboration through a static analyzer (e.g. rubocop or ruby-lint) that uses soft typing (i.e. inferred typing) to determine if a program will crash or not. 2. Performance enhancements through JIT compilation, but preliminary implementations have shown to increase memory consumption as a side effect. 3. Concurrency improvements through better abstractions like streams and pipelines. When used, the running program would place itself inside an event loop, disable the GIL, and force objects to be immutable. Matz calls it Rube Goldberg Programming.