You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am working with grobid, and i tried multi parameters of concurrency and grobid python client's parameter "n".
I found that it is not a accuracy value to find the most suitable paratemers. And the reference manual have only the two client-grobid server and send client. Set the parameters 'concurrency' and 'n' according to the CPU limitations of the respective machine.
So the environment:
grobid server and python-client in a server, what should I set up the parameters 'concurrency' and 'n' ?
I tried multi parameters and didn't find obvious differences.
The text was updated successfully, but these errors were encountered:
AFAIK after you establish the concurrency parameter on the server, the client should follow using the same value.
Yes, I see. However, it based on the server and the client are different machines?(not sure) I mean if the server and the client are the same one machine, whether concurrency parameter should equal to the machine's threads?
For example, if the machine has 16 threads, then there will be tow choices:
@thejiangcj AFAIK You don't need to divide by 2 when the client runs on the same machine as the server. The client's charge on the CPU is lower than the server.
Hello, I am working with grobid, and i tried multi parameters of concurrency and grobid python client's parameter "n".
I found that it is not a accuracy value to find the most suitable paratemers. And the reference manual have only the two client-grobid server and send client. Set the parameters 'concurrency' and 'n' according to the CPU limitations of the respective machine.
So the environment:
grobid server and python-client in a server, what should I set up the parameters 'concurrency' and 'n' ?
I tried multi parameters and didn't find obvious differences.
The text was updated successfully, but these errors were encountered: