Find out soon: dripstat.com
Find out soon: dripstat.com
Interesting post over at the High Scalability blog about Dropbox’s stack.
Everything about it points towards not using python:
1. Needed to mix C with python
2. Had to write custom memory allocator
3. C for inner loops
None of that sounds like something that leads to ‘fast iteration’ (as is implied in the original post).
You see, I paid for those 24 gigs of ram. I don’t want them to go unused.
Yet, my IDE takes up less than a gig.
I want it to take more memory. I am fine with memory hogs. If using more memory means that i can get better features or faster release of products, go ahead take more ram. Ram is cheap.
I want every singly byte of that ram to be filled up.
Today’s release contains an updated Recording Manager with 3 simple tools to help you easily manage your recordings:
‘Pin’ important recordings and periodically ‘cleanup’ to keep only relevant recordings.
Bugfixes and enhancements since 3.8:
3. Event Range and Thread filters in Method History override Global filter.
From the announcement:
The next Limited Update for JDK 7 will be numbered 7u40, and the next 3 CPUs after that will be numbered 7u45, 7u51, and 7u55. The next release will be a Limited Update 7u60, followed by CPUs 7u65, 7u71, and 7u75.
Using digits of PI would be easier to follow…
With today’s release we are adding another major feature that will make debugging much simpler with Chronon.
A lot of times, the amount of data that Chronon shows you in all the views can be overwhelming. While we do have an extensive filter panel in the Method History view, we wanted to provide a simpler, faster way to filter data across all the views. This makes it easier for you to narrow down to the root cause of the issue.
Introducing the ‘Global Event Filter’.
The UI is integrated in the Timeline View. When you create or edit a filter, it is applied to all the views in the Chronon Debugger instantly!
Here is a video demonstrating the Global Event Filter.
Lets see what we have this time:
1. Huge Bugfix for Mockito and Spring Framework
Bug was caused by faulty code generation by the cglib library used by these frameworks. Both the Recorder and Unpacker have been updated to now work around this. If you were seeing a
ClassCastException during recording or a ‘cannot browse to method’ during debugging it was due to this bug.
2. Automatic toString() in Locals view
A long time coming, but finally here!. Now when you click on an array or an object or a string, you will see its contents auto generated as a
toString() in the Locals view. Note that this does not use the
toString() method in your object though.
4. ‘Event’ instead of ‘Time’ in the Debugger UI
The Debugger UI now correctly uses the ‘event’ label everywhere instead of ‘time’ since the ‘time’ value was really an event counter that you were looking at not wall clock time. This also removes the confusion a lot of people had as to whether the ‘time’ value referred to actual clock time.