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
Hi everyone,
I'm working on a mobile AI assistant app called d.ai (decentralized AI) that runs LLMs locally using Llama.cpp. My app processes chat requests in sequence, meaning there's no parallel request handling—just one user input at a time, generating a response before the next input is sent.
Given this setup, I'm wondering about the relevance of the n_batch parameter.
Does it have any impact in a scenario where requests are processed sequentially?
Is it essentially locked at 1 in such a case, making it an irrelevant parameter?
Or does it still affect things like token generation speed, memory usage, or CPU/GPU efficiency?
Any recommendations on best practices for managing batch size in this context (mobile)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everyone,
I'm working on a mobile AI assistant app called d.ai (decentralized AI) that runs LLMs locally using Llama.cpp. My app processes chat requests in sequence, meaning there's no parallel request handling—just one user input at a time, generating a response before the next input is sent.
Given this setup, I'm wondering about the relevance of the n_batch parameter.
Does it have any impact in a scenario where requests are processed sequentially?
Is it essentially locked at 1 in such a case, making it an irrelevant parameter?
Or does it still affect things like token generation speed, memory usage, or CPU/GPU efficiency?
Any recommendations on best practices for managing batch size in this context (mobile)?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions