Is it possible to make asynchronous stored procedure calls to VoltDB using the Python client
up vote
0
down vote
favorite
Is it possible to make asynchronous calls to a stored procedure in VoltDB (an insert in a custom Java Stored procedure) using the Python client?
It looks like it isn't supported but is there a way to not wait for the response, or will I have to move to the Java client for async support?
python asynchronous voltdb
asked Nov 19 at 18:59
StevieB
31
add a comment |
up vote
0
down vote
favorite
Is it possible to make asynchronous calls to a stored procedure in VoltDB (an insert in a custom Java Stored procedure) using the Python client?
It looks like it isn't supported but is there a way to not wait for the response, or will I have to move to the Java client for async support?
python asynchronous voltdb
asked Nov 19 at 18:59
StevieB
31
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is it possible to make asynchronous calls to a stored procedure in VoltDB (an insert in a custom Java Stored procedure) using the Python client?
It looks like it isn't supported but is there a way to not wait for the response, or will I have to move to the Java client for async support?
python asynchronous voltdb
asked Nov 19 at 18:59
StevieB
31
Is it possible to make asynchronous calls to a stored procedure in VoltDB (an insert in a custom Java Stored procedure) using the Python client?
It looks like it isn't supported but is there a way to not wait for the response, or will I have to move to the Java client for async support?
python asynchronous voltdb
python asynchronous voltdb
asked Nov 19 at 18:59
StevieB
31
asked Nov 19 at 18:59
StevieB
31
asked Nov 19 at 18:59
StevieB
31
asked Nov 19 at 18:59
StevieB
31
asked Nov 19 at 18:59
StevieB
31
31
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The VoltDB python client does not support asynchronous calls. It may be possible to make calls from a multi-threaded python application, but we've never tested that, so I don't want to lead you into uncharted waters.
The java, C++, and Go clients support asynchronous calls.
If you're mainly trying to do fast inserts, you might leverage csvloader and you could probably execute csvloader from within a python application, but that's probably not what you're looking to do.
Disclosure: I work at VoltDB.
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The VoltDB python client does not support asynchronous calls. It may be possible to make calls from a multi-threaded python application, but we've never tested that, so I don't want to lead you into uncharted waters.
The java, C++, and Go clients support asynchronous calls.
If you're mainly trying to do fast inserts, you might leverage csvloader and you could probably execute csvloader from within a python application, but that's probably not what you're looking to do.
Disclosure: I work at VoltDB.
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
add a comment |
up vote
0
down vote
accepted
The VoltDB python client does not support asynchronous calls. It may be possible to make calls from a multi-threaded python application, but we've never tested that, so I don't want to lead you into uncharted waters.
The java, C++, and Go clients support asynchronous calls.
If you're mainly trying to do fast inserts, you might leverage csvloader and you could probably execute csvloader from within a python application, but that's probably not what you're looking to do.
Disclosure: I work at VoltDB.
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The VoltDB python client does not support asynchronous calls. It may be possible to make calls from a multi-threaded python application, but we've never tested that, so I don't want to lead you into uncharted waters.
The java, C++, and Go clients support asynchronous calls.
If you're mainly trying to do fast inserts, you might leverage csvloader and you could probably execute csvloader from within a python application, but that's probably not what you're looking to do.
Disclosure: I work at VoltDB.
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
The VoltDB python client does not support asynchronous calls. It may be possible to make calls from a multi-threaded python application, but we've never tested that, so I don't want to lead you into uncharted waters.
The java, C++, and Go clients support asynchronous calls.
If you're mainly trying to do fast inserts, you might leverage csvloader and you could probably execute csvloader from within a python application, but that's probably not what you're looking to do.
Disclosure: I work at VoltDB.
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
answered Nov 19 at 20:34
BenjaminBallard
1,2421011
1,2421011
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
add a comment |
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
Thanks for the reply. I've tried from a multi threaded python application with 50-100 threads so far and it seems to work, but I haven't finished testing yet! We're looking to minimise latency on the inserts, would the csv loader increase latency if working in batches? Looks like will need to move to one of the other clients.
– StevieB
Nov 20 at 11:28
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
For the same request, the latency should be the same regardless of which client is used. But asynchronous requests allow you to send many requests at once so that throughput is not a function of the latency. A multi-threaded client making synchronous requests can also achieve high throughput, but may require a lot of threads to be able to reach the same level as a single-threaded client sending asynchronous requests.
– BenjaminBallard
Nov 20 at 14:07
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
CSVLoader would generally increase the latency, because it would be sending larger batch insert requests into the queues and these take longer to process than individual inserts. You can optionally call a procedure from CSVLoader using the -p parameter, which is usually slightly lower throughput, but can have less impact on latency.
– BenjaminBallard
Nov 20 at 14:08
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381017%2fis-it-possible-to-make-asynchronous-stored-procedure-calls-to-voltdb-using-the-p%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
