Changes between Version 7 and Version 8 of NifDB


Ignore:
Timestamp:
Apr 17, 2012, 10:16:13 AM (13 years ago)
Author:
manualwiki
Comment:

tiny changes in NifDB

Legend:

Unmodified
Added
Removed
Modified
  • NifDB

    v7 v8  
    1 = Using the NIF database back-end = 
     1= Using the NIF database backend = 
    22 
    3 Currently, the Mnesia based back-end is the default, 
    4 therefore you have to specify a command line argument if you would like to use the NIF based back-end. 
     3Currently, the Mnesia based backend is the default, 
     4therefore you have to specify a command line argument if you would like to use the NIF based backend. 
    55 
    66After the system is installed, start !RefactorErl with 
     
    133133will remain the same. 
    134134 
    135 = Comparison with the Mnesia back-end = 
     135= Comparison with the Mnesia backend = 
    136136 
    137 While the [[MnesiaDB|Mnesia]] back-end has been under development longer and can be expected to be more stable, 
    138 it is much slower than the NIF based back-end; 
     137While the [[MnesiaDB|Mnesia]] backend has been under development longer and can be expected to be more stable, 
     138it is much slower than the NIF based backend; 
    139139you can expect about an order of magnitude of speed-up. 
    140 Also, the NIF back-end may require less storage. 
    141 As an indication, loading ejabberd-2.1.8 (6.6 MB on disk) takes '''18323 sec''' and '''566 MB''' of RAM and '''66 MB''' of disk space, while the NIF back-end on the same machine takes '''458 sec''' and '''556 MB''' of RAM and '''52 MB''' of disk space. 
     140Also, the NIF backend may require less storage. 
     141As an indication, loading ejabberd-2.1.8 (6.6 MB on disk) takes '''18323 sec''' and '''566 MB''' of RAM and '''66 MB''' of disk space, while the NIF backend on the same machine takes '''458 sec''' and '''556 MB''' of RAM and '''52 MB''' of disk space.