Book a Demo

Author Topic: v16.1 Project Transfer timing MS Acess vs SQLite  (Read 3779 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
v16.1 Project Transfer timing MS Acess vs SQLite
« on: February 22, 2023, 12:13:26 pm »
We're now investigating using SQLite for our project snapshot clones.  Previously we were transferring our SQL Server repository to a .eapx (MS Access) clone.  This took about 15 mins and produced a file just shy of 2GB (before compaction).  We are now exceeding the 2GB limit, and the transfer fails.  Hence we are looking at SQLite .qea files.

We can transfer the SQL Server repository to a .qea clone, but instead of 15mins it takes 2 hours!!!  (This is with v16.1 32-bit)  One test we ran with 64-bit took 20 hours for the same repository!

Is this to be expected?  Is something wrong with our setup?

TIA,
Paolo and      <--  J o y c e won't play!
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: v16.1 Project Transfer timing MS Acess vs SQLite
« Reply #1 on: February 22, 2023, 08:13:52 pm »
You probably have to ask the Sparx coders...

q.

Mauricio Moya (Arquesoft)

  • EA User
  • **
  • Posts: 344
  • Karma: +8/-4
  • EA Consulting and development in Spanish
    • View Profile
    • Arquehub Azure Module
Re: v16.1 Project Transfer timing MS Acess vs SQLite
« Reply #2 on: February 23, 2023, 07:19:22 am »
I'm not surprised. I've done performance tests with 32-bit and 64-bit versions and the results never show smaller times in 64-bit. Sometimes even longer.