Poor REST performance vs. eXist #17
Comments
|
@IanDavey Could you provide a link to the data and, if possible, the scripts used for these tests? |
|
The data can be found here: https://uscode.house.gov/download/download.shtml (you want the XML link) |
|
The script was continuously changed for each test, but currently I have (with certain items redacted): #!/usr/bin/env python
import base64
import requests
import statistics
import time
REPETITIONS = 100
EXIST_AUTH = 'Basic ' + base64.b64encode(b'*****:*******').decode()
XQUERY = '''<?xml version="1.0" encoding="utf-8"?>
<query xmlns="http://exist.sourceforge.net/NS/exist" cache="no">
<text><![CDATA[
declare default element namespace "http://xml.house.gov/schemas/uslm/1.0";
declare boundary-space preserve;
(# exist:batch-transaction #) {
(: redacted :)
}
]]></text>
</query>
'''
def timed_send(fn, port):
start = time.time()
response = requests.delete(f'http://localhost:{port}/exist/rest/db/test/{fn}', headers={'Authorization': EXIST_AUTH})
assert response.status_code < 300, response.reason + '\n' + response.text
result = response.text
end = time.time()
with open(fn, 'rb') as f:
response = requests.put(f'http://localhost:{port}/exist/rest/db/test/{fn}', f, headers={'Content-Type': 'application/xml', 'Authorization': EXIST_AUTH})
assert response.status_code < 300, response.reason + '\n' + response.text
return end - start
def output_stats(label, dataset):
print(f'{label}:')
print(f'\tMinimum: {min(dataset)} s')
print(f'\tMaximum: {max(dataset)} s')
print(f'\tMean: {statistics.mean(dataset)} s')
print(f'\tMedian: {statistics.median(dataset)} s')
if REPETITIONS > 1: print(f'\tStddev: {statistics.stdev(dataset)} s')
usc01_exist, usc01_fusion, usc42_exist, usc42_fusion = [], [], [], []
for _ in range(REPETITIONS):
usc01_exist.append(timed_send('usc01.xml', 8080))
usc01_fusion.append(timed_send('usc01.xml', 4059))
usc42_exist.append(timed_send('usc42.xml', 8080))
usc42_fusion.append(timed_send('usc42.xml', 4059))
output_stats('1 U.S.C. eXist', usc01_exist)
output_stats('1 U.S.C. Fusion', usc01_fusion)
output_stats('42 U.S.C. eXist', usc42_exist)
output_stats('42 U.S.C. Fusion', usc42_fusion) |
|
Hi @IanDavey can you tell me which version of FusionDB you tested this against? If you are not using a nightly build, then as recently discussed with Grant, the nightly builds should have much better performance than Alpha3. |
|
It was Alpha 3. That makes sense. I'll retest with the nightly. |
|
Thanks @IanDavey much appreciated. |
|
@adamretter Just to confirm — is the latest nightly from 11/25? That's what's showing up on the link you sent us. |
|
@IanDavey Yes, that's right. We have been working on a change which has taken more engineering than expected, but we hope to have that pushed in the next few days - so there will then be a new nightly. |
|
@adamretter Just checking in — has there been anything new on this? |
I have been benchmarking different types of requests to the RESTful API for both Fusion and eXist, using the latest USLM versions of titles 1 (a short one) and 42 (the longest one) of the US Code. Each of these tests had 100 repetitions, and both eXist and Fusion were identically configured on the same VM.
First, I tested a simple PUT of a document to
/exist/rest/db/test:Next, I tested GET:
Then, I POSTed some XQuery to get a specific section of a document:
(the XQuery I used was an adapted version of a giant block we're using for a client that does a bunch of pre- and post-processing, but the most relevant piece is
//*[@identifier=$identifier], and this is an indexed attribute)Finally, I ran a DELETE (PUTting the document back between repetitions, but only timing the DELETE):
It appears that Fusion's running time across the board grows faster than eXist with respect to document size. As several of Xcential's use cases involve handling large-ish documents, as a result we currently can't recommend Fusion over eXist to clients (which is a unfortunate, because in other POST XQuery tests, such as generating a small top-level outline for all USC titles, Fusion is faster).
The text was updated successfully, but these errors were encountered: