Upload traces through the browser

On the console Analyses page, you upload one or more traces, as single files, compressed or in a folder. The page sends the files in chunks of up to 8 MiB and, if the connection drops, picks up where it stopped.

Before you start

• A console account, with two-step verification set up and the terms accepted (first sign-in).
• A browser with JavaScript turned on. Without it, the upload works with fewer features (without JavaScript).
• The traces on your computer (find the trace file). The page shows your account limits below the upload button (limits).

Upload the files

1. Open https://app.waitscope.com/ and sign in: the Analyses page opens.
2. In the New analysis panel, click Choose files or Choose folder, or drag the files or the folder to Drag the traces here.
3. Check the summary below the buttons, such as 3 files selected (1.2 GiB). If there are .trm files, the summary says how many are left out.
4. Click Upload and analyze.
5. If the page asks Are these traces from the same process?, choose Yes, same process: analyze together or No, analyze each trace separately (when to analyze together).
6. Wait for the bar to finish with the page open. During the upload, Uploading: 35%. Do not close the page. appears, with the current percentage.

Result: when the upload creates a single analysis, including a collection, its page opens, with the processing and then the report. With several analyses, the Analyses page comes back with the message Files received. The analyses start shortly. With a zip or tar, the message is File received. The analysis starts shortly. The analyses appear under History.

The question about the process appears when you choose more than one trace, or a compressed file with more than one trace inside. With a single file, the page uploads right away.

Chunked upload and resume

The page sends one chunk of up to 8 MiB at a time, and the bar shows the progress of the whole upload. If the connection drops, Upload interrupted. Retrying in 4 s from where it stopped. appears: the page asks the server how much has arrived and continues from there, with waits that grow from 1 to 30 seconds, for up to 12 attempts in a row.

If the attempts run out, The connection to the server dropped. Send the same files again to continue from where it stopped. appears. Choose the same files, give the same answer to the question about the process and click Upload and analyze again: the upload continues from the point where it stopped. Choosing other files cancels the previous upload.

What has already arrived is kept while your browser session lasts, for up to 24 hours without a new chunk. Signing out of the console, or letting the session expire from inactivity, deletes the half-finished upload.

Processing queue

Each analysis enters a queue on the server and goes through queued and processing until it ends as done or error. The server first takes the analyses of whoever has the fewest analyses running: someone who uploads many large files does not hold up the queue for others.

• The analysis page shows the percentage of the file already read and refreshes itself every 2 seconds, or every 10 seconds with the tab hidden. At the end, it opens the report or the error.
• History refreshes itself while there is an analysis queued or running, without reloading the page: the checked analyses, the upload in progress and the scroll position stay as they are.
• You can close the page: the analysis continues on the server.
• Each analysis has up to 60 minutes of processing (limits).

Without JavaScript

The pages work without JavaScript, with fewer features:

• The form sends all files in a single request, with no progress bar and no resume: if the connection drops, upload again.
• There is no question about the process. To combine the files into a single analysis, check Analyze together, as a single collection before uploading.
• The analysis page does not refresh itself: use the Refresh button.

Common problems

• Choose at least one trace file. No file with content was chosen: .trm files, hidden files and empty files do not count.
• File too large. The total size of the files exceeds the per-upload limit: compress them with gz, bz2 or zip, or split them into smaller uploads.
• Queue full, Analysis limit or Too many analyses. Wait for analyses to finish or delete old analyses with Delete selected. See all the messages in limit messages.
• The analysis page shows an error. The reason appears at the top, and the uploaded file has already been deleted: fix it and upload again (file that is not a trace).

Next steps

• Read the report, starting with the Summary.
• For several files from the same operation: analyze together.
• To upload from your phone: upload with the Android app.