[Slow performance] - two seconds for each call

Open
#76 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reproducing the reported two-second timing for single-product and 100-product wcapi calls, then inspect the wrapper's connection setup and request path. Done means identifying whether connection establishment causes the fixed delay and documenting or testing a change that reduces per-call latency.

Written by the indexing model from the issue text.

Description

Hi,
In my tests, each wcapi call takes about 2 seconds, regardless of the content of the call.
If I do a get of a single product or a get of 100 products, it always takes about 2 seconds.

Two seconds for an operation on 100 products can be an acceptable time, however it is far too long for an operation on only one product.

The fact that the long execution time does not depend on the type of call, makes me rule out a problem on my server, and makes me think that most of the time is used to "establish the connection" and not to "execute the query".

Can i do something to speed up the process?

Thanks

Dominant language
Python
Stars
216
Forks
108
Avg merge
6h 34m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from woocommerce/wc-api-python

All issues in woocommerce/wc-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.