summaryrefslogtreecommitdiffstats
path: root/chrome/test/perf
Commit message (Collapse)AuthorAgeFilesLines
* Add deps files and rules for the checkdeps script.brettw@google.com2008-08-081-0/+3
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@600 0039d316-1c4b-4281-b951-d872f2087c98
* Don't link directly against GetPerformanceInfo so that win2k can be happy.mbelshe@google.com2008-08-061-4/+29
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@449 0039d316-1c4b-4281-b951-d872f2087c98
* Fix win2k testers by commenting out a function that is not supportednsylvain@google.com2008-08-061-3/+4
| | | | | | | on windows 2000. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@439 0039d316-1c4b-4281-b951-d872f2087c98
* Initial version of a chrome memory test. This is not yet done; as it stillmbelshe@google.com2008-08-052-4/+18
| | | | | | | | | | | | | | | | | | | | | | causes intermittent chrome crashes. But, checking in an intermediate step so that others can play with it too. Basic concept is to have a pre-loaded replay cache with interesting data. This test then drives chrome through automation, simulating a sequence of pages in each tab in a way that a user might also do so; this allows us to get per-tab caching of data similar to what the user would see. Includes a logged in gmail session, a few pages that exercise some javascript, several languages, and pages from many mainstream sites. Lots more can be done with this test going forward; for now the goal is to just measure and track memory. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@361 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome to the repository.initial.commit2008-07-265-0/+621
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15 0039d316-1c4b-4281-b951-d872f2087c98