Slowness on Octoprint API

[crashburn65]

Hi all,

I'm on the devel branch.

When I'm printing a job, uploading a file as well as querying the printer (api/job) both via the API, I'm getting Timeout::Errors.

Is there currently multi-threaded support or are there plans for one?

[foosel]

The communication with the printer already happens in its own thread. What's the load on the system?

[crashburn65]

An average of 0.87 on a 512MB Raspi (Octopi image).

Initially I suspected that it was an IO issue, but iotop doesn't point to any anomaly.

[foosel]

Might also be something related to #357

Otherwise, I'm a bit at a loss. Will try to do some testing ASAP to see if I can reproduce it on a Pi -- no luck locally.

[foosel]

Do you also see symptoms as described in #390 ?

[foosel]

@davidchua Still waiting for feedback here ;)

[crashburn65]

Hi @foosel sorry I dropped the ball here, had a busy month and missed the notifications.

I'm back now :)

Its not the same as #390. My load average is < 1 at all 3 intervals. The highest peak I got was about 40-50% CPU usage on the python octoprint thread on my Raspi 512MB.

I'm still having this problem. A simple HTTP GET to /api/job for example can take up to 10-30 seconds to return.

I've just added benchmarking on my app that utilizes the API, will get back to you in a day or two with actual results.

[foosel]

@davidchua any update here?

[foosel]

Closing until more information is available (e.g. the mentioned benchmarking results) since for the life of me I can't reproduce that at all.