AISWare MDB enables customers to take preemptive opportunity in age of IoT

Customer requirement

A group-level operator is not able to support the capacity and performance of billing run for more than 30 provinces and 400 zones nationwide. Such task needs to be split into 3 batches in a row and operation staff needs to manually change scheduling based on performance load. It takes more than 17 hours. Focus of requirement on database is: 1. Supports massive data access for more than 400 zones in parallel; 2. Extreme performance is required so as to shorten billing run time elapse

Construction Plan

The operator introduces AISWare MDB to replace existing OLTP. The thread pool in AISWare MDB occupies less system resource and has more throughput, compared to usage of a single client connected to a single thread. Collaboration model in AISWare MDB is able to be switched by coding at application level without impacting the core, when switching context. When used together with thread pool, issues caused by thread pool like shaking or dead lock can be resolved and it’s able to support millions of connections. Section based index in AISWare MDB uses B-Link-tree algorithm and performs read and write in parallel. It’s not required to lock entire tree or the path from root to specified node when modifying b-tree, which dramatically improves simultaneous performance of access to section index. Meanwhile, the merging and recycling of nodes tries to minimize memory occupation. Hash indexing in AISWare MDB supports dynamic hash. Hash index space is gradually scaled up when using hash index, so that hash algorithm can always be kept linear. Meanwhile, rehash is applied to avoid table locks. MVCC in AISWare MDB isolates read and write transactions, that read transaction doesn’t necessarily request read lock; in the case of massive simultaneous writes, MVCC algorithm prevails than other algorithms.

Application Effect

  • Improved performance for simultaneous transactions

    Supported billing run in parallel for more than 30 provinces and 400 zones.

  • Improved performance

    By means of AISWare MDB indexing and MVCC algorithm, the throughput reaches out to 100,000 CDRs/s, and billing run takes less duration from 17+ hours to within 2 hours.