The profiler's data blob is a massive, gigantic blob of json (ls the
file and you'll see).
You can easily search&replace the urls to point at local files instead
of the CDN.
Alternatively, there's a qt-based profiler up on tadzik's github that
can read the json blob (you will have to
--profile-filename=blahblah.json to get that), but it doesn't evaluate
as much of the data - it'll potentially even fail completely what with
the recent changes i made :S
The biggest contributor to filesize for the profiler is the complexity
of the call tree. If you can cut out parts and pieces of your program,
you should be able to profile them individually just fine.
In my experience, firefox is more likely to work with the big profiles.
If anybody is interested in improving our html/js profiler front-end,
please do speak up and you'll be showered with as much guidance and
praise as you need :)
- Timo
