Fast TikTok API (free-watermark videos)
Pricing
$38.00/month + usage
Fast TikTok API (free-watermark videos)
Fastest TikTok API for Trend, Hashtag, Search, Music, User, Comment. Real-time, authentic data. No pre-built databases. Provides no-watermark video download links.
5.0 (3)
Pricing
$38.00/month + usage
32
Total users
1.2k
Monthly users
93
Runs succeeded
>99%
Response time
3.4 hours
Last modified
4 days ago
Increased spending per day
Open
Hello,
I have an issue regarding the bills. Our quota consumed rapidly since March 26. I noticed that since this date there are extra writes to the key-value store increased 3 times per day than the previous period. And nothing changed from ourside.
Can you please help us addressing this issue?
Thank you, Mahmoud
Hi @acumen,
Thank you for reporting this issue.
Yes, we've recently implemented a change to reduce costs in situations where an "Apify Actor run" might be migrated to another host.
As you know, in some cases, an "Apify Actor run" can be stopped and moved to another host as part of their optimization strategy. This can lead to an Actor run consuming double the resource cost because it might scrape the same record twice. Therefore, we're using a key-value store to persist the Actor run's state and avoid this potential double cost.
We have a blog post about this: https://novidevelop.github.io/blog/apify-actor-container-migration-data-reliability
We will investigate this further to find a better way to optimize this process.
There is also a tip that you could reduce the spending: Reduce memory (RAM). Our actors are optimized in depth, so you can try an amount of memory which fit to you. Mostly, we see it runs well with 256MB for around 100 records.
Thank you for using our service!
Novi
Hello,
We have just released an improved version. Could you please help us check whether the running cost is reduced?
acumen
Hello @novi,
Thank you for your efforts. I’ve attached two files, one of them shows the changes in costs. As you can see, the most significant changes are in the "key-value store writes". I checked the last four days, and nothing changed. Since April 8th, I’ve reduced the interval of updates from every hour to every two hours to reduce costs, but the "key-value store writes" remain high as you can see in the second screenshot.
Thanks
Hello @acumen,
Thank you for your information. We have update our logic to avoid initiate the KEY-VALUE store. This process will only be executed in case of migration event.
We believe this will reduce the expense cost.
Thank you for your support.
Novi
Hello @acumen,
Could you help us check whether our recently update helps you reduce cost?
Thank you so much!
