Open boxabirds opened 5 years ago
I had trouble getting a stable running system with RAM as high as 26GB on a default instance out on GCP. Once I upgraded to 52GB, it seemed to run fine.
I had trouble getting a stable running system with RAM as high as 26GB on a default instance out on GCP. Once I upgraded to 52GB, it seemed to run fine.
@kevin-rowney thank you! Is this an inference-only setup or was it also doing fine-tuning? I'm thinking it makes sense to separate inference-only as it seems at least on my local machine to work happily in "only a few GB") with any additional fine-tuning.
Have you had much experience with resource consumption with multiple workers?
I was having a heck of a time getting this working on GCP. Tried every option they've got. Was also working fine on my local machine (32g ram, 3.5 GHz Intel Core i5, 4 cores). Thanks to the suggestion above, it seems to be working reliably now:
GCP: Compute Engine: VM n1-highmem-8 (8 vCPUs, 52 GB memory)
Wish I could make it work in the various container services... but no luck there. Can't remember if i tried exactly the same config there though... will need to give that a try. Don't think i went up as high as 52gb.
Hi all I want to profile the memory usage of bert-as-a-service so I can do some budget calculations. A single worker on my Mac when starting up seemed to take upwards of peak 20GB and stable of 6GB.
Has anyone done any more exhaustive analysis on the memory footprint of this?
More concretely, when people have deployed this to say, AWS, what sized EC2 instance worked well?
thanks in advance!