Open ice-melt opened 5 years ago
I'm getting it as well. The threads appear to report that they are "ready and listening!" but the client hangs when I try to connect. Wondering if it's because I don't have enough RAM on this instance. Am all the way up to a 13GB RAM instance, so maybe I should try for 16GB....or larger?
@ice-melt: How much RAM was on your system when you ran this?
Same issue here with 6GB of RAM
Same issue
I had the same issue, with 8GB machine, after upgraded to 32GB and I'm able to run with 2 workers.
However, when running more than 2 workers on 8 Cores 32GB machine, the issue appears again.
There are heaps of memory available
See the log below
(bert-as-service) sh-4.2$ bert-serving-start -model_dir ./multi_cased_L-12_H-768_A-12 -num_worker=3 -cpu ............. OMP: Info #250: KMP_AFFINITY: pid 26690 tid 26690 thread 0 bound to OS proc set 0 OMP: Info #250: KMP_AFFINITY: pid 26687 tid 26753 thread 1 bound to OS proc set 1 OMP: Info #250: KMP_AFFINITY: pid 26690 tid 26776 thread 1 bound to OS proc set 1 OMP: Info #250: KMP_AFFINITY: pid 26684 tid 26751 thread 1 bound to OS proc set 1 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc I:WORKER-2:[i:gen:558]:ready and listening! I0913 06:26:32.240278 140128425056000 init.py:558] ready and listening! I:WORKER-0:[i:gen:558]:ready and listening! I0913 06:26:32.241424 140128156620544 init.py:558] ready and listening!
i had the same issue, with 8Cores 16GB machine
I solved this porblem with seting overcommit_memory to 0 on my linux machine,you could do this when you have enough memory.
std::bad_alloc
),how can i fix it?