Hosting config Question

[Ronnie Machio]

Hey Guys I need some advice.
I have a WordPress blog that I am running a sports data and scores service on. currently, I am on google cloud running a config of 100gb harddisk and 16gb ram. My site uses an API service to get the data using JSON. I have it set to call for data once a day (bulk) and a scores update running every 10 hours. For this, we are consuming about 100k most of the bulk are during the major daily update. My problem is during this time and about 1 hour later my site will be inaccessible basically it crashes (timeout errors) but for the rest of the 24 hours, it runs fine.
On the WordPress end, we are using a caching plugin and a varnish cache on the server end. I would like to scale the site to offer more sports. Most of everyone that I talk to thinks this is a memory issue. currently with the above setup am paying $70-120 a month depending on traffic. What would your advice be on hosting because I would like to do dedicated maybe up the memory to 48-96GB around there but my budget is around $100-150 a month? If I could find something cheaper I would definitely go for it. Anyone got any advice for me on configs or what I can do to solve my memory issues??
Thanks

 

[TwitchPro]

okay so basically you need a secondary vm that handles the bulk api calls and then store that data in a database that your web client can access. alternatively you could use a container instance for your web client and then make a container for your bulk api call so the processing doesnt affect the other. for some reason heavy processing for outbound traffic with php can cause this.

 

[Ronnie Machio]

okay so basically you need a secondary vm that handles the bulk api calls and then store that data in a database that your web client can access. alternatively you could use a container instance for your web client and then make a container for your bulk api call so the processing doesnt affect the other. for some reason heavy processing for outbound traffic with php can cause this.

thanks, I would never have thought of that. but I have a way forward now