muymoo / profile-it Goto Github PK

currently all we use are millis (and look at ns, query, updateobj)... more interesting info like lock stats, number of scanned/moved/updated things... etc.

all available things in system.profile
http://docs.mongodb.org/manual/reference/database-profiler/#output-reference

potentially interesting:
ntoreturn, nscanned, scanAndOrder, moved, nmoved, nupdated,
keyUpdates, lockStats, nreturned, responseLength, millis, ntoskip

probably not:
ts, cursorid, client, user

pretty gnarly now.... starting to get out of hand

this is getting a bit excessive and gross with long urls... we could store state in a service or something instead of passing it all around via ui-router.

@muymoo I'm all set up to go now and I'll be working on this later tonight.... right now runs/profile doesn't work for me so I can look into that (maybe a permission-y thing)

suggestions on next steps? idk where you're at exactly

remove timestamps and things that wont' happen more than once (just keep structure)

Progress bar looks great, but I'm getting a 404 for the flamegraph... I saw this before occasionally, it's like the Angular binding with that svg data isn't working all the time.

@lrbridge Even though dtrace is running fine and the runTests method is being called, there is nothing showing up in the out.stacks file.

@muymoo - just fyi what i'm working on

Starting at the top left graph, the drilldown sequence makes sense (at least to me :) ). But there are other drilldown-ish patterns... like on the top right. The top right is implemented but it doesn't make sense with how the up buttons work.

Need to think about what the experience should be like... what drill down is like