This is good information thank you, we at a point where the follow tactics must be implemented to the api calls too 
Yeah it’s sort of ridiculous, but IG is really making us focus on scraper accounts. We’re forced to look at quality, api calls, limits, user filters, etc. Before it was churn and burn (and it still somewhat is,) but going down that rabbit hole can make you lose a lot of money.
What about story viewing?
UPDATE
I am losing about 1-2 out of 135 scrapers a day, but these are scrapers that I created from my own bot. My purchased scrapers are STILL alive. These settings seem to be working fine for me 
.
Also shoutout to @xstaC for making me think a little more about User Filters.
I removed a good amount of User Filters and only focused on the ones I REALLY need. By doing this I substantially lowered my api calls, JV is searching for followers a lot quicker, I’m coming closer to my daily limit, and I may be able to lower my ratio of 5:1 to something lower.
2 Likes
Currently doing 75-100 story views. Still sometimes I do not reach daily limits because my child accounts are now using max 1 API call every 2 seconds (with a delay of up to 7 seconds if it reaches this limit)
But removing Likes and cutting story views down to half has helped. Still working on optimal settings so we can get 200 follows and very low amount of scraper bans
Also having 600+ scrapers on Jarvee is causing it to have a seizure, so wasting a lot of time waiting for Jarvee to load lol, so working that out too
1 Like
Use a dedi server with at least 32gb or RAM and SSD. Trust me, it will fly with 2000 accounts (not with 600)
How many users are you able to scrape with those ? Around 20-30k users per day ?
Seems like a big headache to deal with
I’m using Dedicated 64GB DDR4 RAM, 2 x 512GB NVMe SSD, AMD Ryzen 5 3600 (6-core) from Hetzner (AX41-NVME)
The PC actually runs fast, but Jarvee is reallllyyy slow
All accounts using API, but as soon as I have more than 550+ scrapers, Jarvee can become almost unusable at times. It can take 5 minutes to even tick a box and that’s if it doesn’t crash, even with my super duper server.
How are you able to run 2,000 accounts?!
Yeah it is. I’m trying to setup 1k child accounts for 1 mother, but atm I’m only on 150 childs and 600 scrapers because of VPS issues … (and currently testing scrapers made with Jarvee since I was spending too much money on providers here)
Have you tried removing Jarvee from Windows Defender security?
Then it will be 4k+ scrapers for 1000 childs, things go way to dark
Yes this doesn’t help. CPU running at like 2% but Jarvee freezing once I put too many accounts on.
@denis1 Then it will be 4k+ scrapers for 1000 childs, things go way to dark
I’m prepared to get 4k scrapers, it is what it is 
1 Like
do you have the the accounts “grouped by tag”? cause this is killing performance turn it off and it will run way better - i am running on 10 servers each 250-400 accounts plus the scrapers. with “stable” jarvee
1 Like
100% agree - not sure if this is a new thing but over the past couple of weeks we have noticed if you have this checked its pretty much game over for the system - no matter what server you use.
1 Like
it was since years like that - but with more and more accounts in it #scraper it because worse and worse 
1 Like
Yeah now that I think about it we have never even used that GROUPING filter until these scraper issues 
1 Like
Wow! Yes it was switched on. What a difference this has made. Thank you 
1 Like
you’re welcome buddy
as far as is understood it is due to everytime when you “click” on a tab where “group by tag” is used it has to recreate it - sobasically it “start the process of grouping and loading them like that” every time you open one of the tabs (socialprofile tab/ tool tab) again. which looks i is an intense process
2 Likes
+1 from me here, so far been using only filter by tag for batches of 20-50
This really did help
Could you solve this?