-
Notifications
You must be signed in to change notification settings - Fork 16
PerformanceJSON
Kritpon was build with perfomance in mind. This is the reason that prompted me to use Annotation Processor. As already state, Kripton use Jackon parser/serializer at low level to transform Java bean in persistence format like JSON, CBOR, YAML, PROPERTIES.
The Xml parser/serializer was taken from xmlpull.org.
At the moment, only JSON performances are tested. To accomplish this, benchmark application of [LoganSquare] was extended (https://github.com/bluelinelabs/LoganSquare) with the aim to evaluate Kripton Performance on different devices.
You will find compiled version of Kripton Benchmark on Play store.
QR code
Direct link
You will find original benchmark demo LoganSquare/BenchmarkDemo.
The results are fantastic!!!!
Krypton wins in almost many tests (although in some cases it is very close to the second)!
The reason to use Kripton instead of other persistence libraries is that no other library allow you to manage persistence through JSON, XML, etc, SQLite and SharedPreferences with an unique and coherent set of annotation and interfaces.
There are some test both for serialization and deserialization. Each test is repeated 20 times. For each library there's a bar. Kripton's bar color is yellow. For each test you will find mediumn, max time and min execution time. The bar rapresents medium values. Lower, obiousily is better.
- Introduction
- Goals & Features
- Kotlin
- Immutable or Mutable Pojo
- Annotation Processor Args
- Credits
- Articles
- Benchmarks
- Setup
- Tutorial
- Usage
- Dependencies and inspirations
- Stackoverflow
- Documentation
- SQL logging
- Data source options
- Indices
- SQL Type adapter
- Global SQL Type adapter
- Constraints
- Live data: welcome Architectural components!!
- Paged Live data
- Dynamic parts
- Transactional and batch operations
- Async Transactional and batch operations
- Global transaction
- Support for immutable POJO
- Generate Content provider
- Generate Database schema generation
- Database migration
- BindSqlColumn
- BindContentProvider
- BindContentProviderEntry
- BindContentProviderPath
- BindDao
- BindDaoMany2Many
- BindDataSource
- BindDataSourceOptions
- BindDataSourceUpdateTask
- BindIndex
- BindSqlRelation
- BindSqlAdapter
- BindSqlChildSelect
- BindSqlDelete
- BindSqlDynamicOrderBy
- BindSqlDynamicWhere
- BindSqlDynamicWhereParams
- BindSqlInsert
- BindSqlPageSize
- BindSqlParam
- BindSqlSelect
- BindSqlUpdate
- BindSqlType
- BindSqlTransaction