Pay $3.00 for 1,000 results
Zillow Detail Scraper
Pay $3.00 for 1,000 results
Get details of Zillow properties from URLs. This Actor can be easily integrated with other Zillow Scrapers.
Reusing actor between runs
Open
Hi, because of the nature of our product we can not use batch searches - we have to submit each query one at a time. It looks like the building of the actor takes most of the time:
actor = client.actor(APIFY_ACTOR_ID)
And the running itself is very short.
My questions is: is there a way to keep the actor alive, so that we only do the run part every time and avoid the long build times?
kevin_eso
following. same thing here. it's currently 30s roundtrip
Hi, thank you for your interest.
Firstly, regarding the code snippet: apifyClient.actor(APIFY_ACTOR_ID) really shouldn't take any noticeable time - it just creates a "subclient" for the Actor, that provides methods for starting the Actor etc. It's most likely the await actorClient.run(input) (or .start) that takes the time. Can you please check that what you describe really the case? If so, we will definitely fix that, but I'm not aware of any such issue currently.
However, you are right that starting a new run of the Actor every time you need to scrape one URL is quite inefficient and slow. So-called "standby" Actors, that are always ready to receive one URL/search address, scrape it, and quickly respond with the data, are something that we are currently exploring and should be available at some point this year, but I'm not certain about the exact timeline.
I hope this helps, I'm keeping this issue open and we'll reach out as soon as we have any update on this.
Maximillian Copelli- 56 monthly users
- 99.8% runs succeeded
- 8.3 days response time
- Created in Jun 2023
- Modified 28 days ago
