I added it as a proof of concept, and a temporary solution to retrofit our
current API to make it more consumable. Unfortunately, i don't think
there's any sane way for it to become supported, and we should instead
focus on a first-class REST-like API. I realized while we intended to do
this, we
What is the history/origin of /apibeta anyways?
On Mon, Dec 29, 2014 at 1:32 PM, Isaac Councill wrote:
> Ok, here's code for the pure json apibeta bench. I realized it was a bit
> unfair because I was making concurrent requests (max 3). Stripping out all
> concurrency, it's coming in at 17.2sec.
Ok, here's code for the pure json apibeta bench. I realized it was a bit
unfair because I was making concurrent requests (max 3). Stripping out all
concurrency, it's coming in at 17.2sec.
drop in src/aurora/, no dependencies required.
go build o build -o dist/aurora2 aurora/client2/bench
dist/aur
Here's source from go thrift (warning: very ugly). I had to make a few
modifications to the ttypes and client libraries to get it working. It
requires git.apache.org/thrift.git from the 0.9.2 tree (0.9.1 generates
code that is much farther from correct).
after putting it in src/aurora/client:
go b
Hey Isaac
Would love to hear your pain points with Thrift and also can you share your
source for the test clients
-Jake
On Mon, Dec 29, 2014 at 1:27 AM, Isaac Councill wrote:
> tl;dr;
> apibeta seems way faster (and arguably better) than thrift api. What are
> the long term objectives for apibe
Interesting data, any chance you could share the source of these benchmarks
for others to reproduce? Can you confirm you used the getTaskStatus API
call with the same TaskQuery for both the JSON and the thrift client calls?
On Sun, Dec 28, 2014 at 10:27 PM, Isaac Councill wrote:
> tl;dr;
> apibe
