On Thu, Dec 18, 2014 at 2:14 AM, Christian Grün <christian.gruen@gmail.com> wrote:

>> 4) With my database, on a t2.micro EC2 instance (1 VCPU + 1 Go RAM),
>> BaseX is unusable.
>
> That's a good hint. What does "unusable" mean? Did you encounter
> problems to create the database, or are your queries running out of
> memory?

"unusable" means "incredibly slow", the same request which takes 1.5 sec on my shared server takes 30 sec on the micro instance.

For more speed, I tried to partition my database in multiple little databases, and my results are surprising for the same request:

database size | shared CentOS    | t2.micro EC2 CoreOS
2.4 Go        | 1.5 sec 160% CPU | 30 sec
254 Mo        | 0.35 sec 35% CPU | 0.21 sec
224 Ko        | 0.24 sec  2% CPU | 0.14 sec

It seems that the database size has a huge impact on BaseX performances, is there somewhere a summary about BaseX good practices (database size and number of resource files) ?

Best regards

Florent

--
FLOSS Engineer & Lawyer