329714 - check for performance impact

Status: RESOLVED FIXED

(Toolkit :: Safe Browsing, enhancement)

Description

[Fritz Schneider]

Are we impacting page load time? 

One way we could check this is by modifying the loggifyer code (see debug.js) to automatically profile. We can see how much time we're taking in each function we call on the critical path (progresslistener, etc). 

This is a cool task in and of itself. The loggifyer could easily be augmented to do very interesting profiling stuff.

Comment 1

[Dave Townsend [:mossop]]

I've been using this for a couple of days, and though I can't be totally certain that it's this that is causing my issues ever since I've started using it I've quite often found that firefox is suddenly using 50% CPU time when it's not actually doing anything. Even with all tabs closed. It continues like that for a couple of minutes then drops off again.

As I say I cant definitely say its this, but I dont recall seeing this before I enabled this extension.

If you have any suggestions to try to track this down then I'm glad to help out.

Comment 2

[Justin Dolske [:Dolske]]

Other bugs have radically improved SB performance over the years. Nothing specific to do here.