Hi Sergey,
I was not aware of ShowSlow's functionality to run Firefox
automatically and at the time I saw ShowSlow, it had a lot less
functionality than it currently does now.

My original intentions for Cesium were for it to run Firefox
headlessly and automatically, be configurable via a web ui, graph
results over time, have an API, and run on an intranet as part of a
continuous integration tool. It's size and scope has increased
considerably and certainly does overlap with ShowSlow's. I certainly
never had the intentions of competing or simply duplicating ShowSlow.

Combining our efforts would certainly be beneficial for the
performance community. Can we discuss this off-list?

Thanks,
Ryan


On Jul 17, 2009, at 2:57 PM, Sergey Chernyshev wrote:

>
> On Thu, Jul 9, 2009 at 11:24 PM, Ryan Doherty <rdoherty@...>
> wrote:
> Yeah, we had checked out ShowSlow before and during the creation of
> Cesium.
>
> There are a few key features that Cesium has that ShowSlow doesn't:
>
> * Automatic testing - you don't have to remember to test your sites
> * No issues with privacy (ShowSlow requires ySlow to beacon to it
> every site you visit)
>
> Ryan,
>
> I think there is a confusion here - ShowSlow.com is a public service
> that lets everyone try ShowSlow tool which in turn is an open source
> tool (primarily because I created it for internal use and had those
> privacy issues in mind).
>
> More over, my internal use is a simple script (actually part of
> ShowSlow code) that runs Firefox periodically on the list of URLs
(http://code.google.com/p/showslow/source/browse/trunk/showslow.sh
> ). so it actually is used for automatic testing and that's how data
> in ShowSlow is created for some URLs (I can't run it for all URLs
> submitted due to financial constraints ;)).
>
> When I saw that you're from Mozilla, I thought you've created a
> XULRunner app or something similar to automate YSlow-ing, but now I
> opened the zip file I see that it's similar to ShowSlow in it's
> concept actually.
>
> Main business goal for ShowSlow is to let teams of web developers to
> see how their sites are doing and their business bosses to be able
> to monitor performance over time without knowing all the technical
> details. This is why ShowSlow is not conceptually limited to YSlow
> and is going to be displaying any metric that is reasonable.
>
> In addition to drawing results of the monitoring, it has a feature
> that I think is also very important - it allows tracking of the
> custom events so it becomes easier to analyze what caused changes in
> metrics. You can see a public beacon
here:http://www.showslow.com/beacon/events/
> and you can see example events
here:http://www.showslow.com/details/?url=http%3A%2F%2Fwww.sergeychernyshev.com%\
2Fblog%2F
>
> I clearly see my mistake in not meaking it obvious that ShowSlow is
> open source project. In my plans is to create a wiki-based site on
http://www.showslow.org/so
> all this can be documented properly and all.
>
> I'll be happy to help your team to install ShowSlow if you're
> interested and I'd be happy to join forces with you guys or somehow
> else combine our efforts so we don't spend our time building the
> same tools.
>
> Thank you,
>
> Sergey
>
>
> --
> Sergey Chernyshev
> http://www.sergeychernyshev.com/
>
>
>
>
> Future ideas:
> * API - allowing you to pull out performance data and use it anywhere
> you want
> * Accounts - setup your own sites and configuration
> * Customizable homepage
>
>
> -Ryan
>
>
>
> On Jul 9, 2009, at 6:48 PM, Philip Tellis wrote:
>
> >
> >
> > Have you had a look at ShowSlow?
> >
> > RD dropped bits saying:
> >
>
>
>

Ryan Doherty
rdoherty@...