1 Introduction
Ignite is an implementation of a distributed memory grid. It is based on the Java platform and has the characteristics of persistence, distributed transactions, and distributed computing. In addition, it also supports rich key-value storage and SQL syntax (based on the h2 engine), which can Think of it as a distributed memory database.
2 Basic use
There are two ways to use ignite: one is to download the release version program from the official website, decompress and run the deployment, and the other is to integrate it into existing applications through embedded.
3 common commands
| Order | Function |
|---|---|
| top | View the cluster network topology |
| cache | Check the overall cache status |
| config | View node configuration |
| open | Open a configuration file to connect to the cluster |
| close | close the connection |
4 jjava client accesses ignite
4.1 Reference jar package
ignite-core-2.10.0.jar and cache-api-1.0.0.jar packages
4.2 Write client program
Hardware conditions Both the server and the client are on a stand-alone win10 operating system
cpu: 4 cores and 8 threads, memory 32G, disk and solid state drive are sufficient.
Prepare first, 1 million, 5 million, 8 million, 14 million data volume
Single client concurrently fetches data results with 100 threads
100 clients concurrently fetch results
5 summary
First of all, from the simple test in Chapter 4, it can be seen that the time for ignite to access data does not increase as the amount of data increases.
The second test is that the server and the client are on the same machine without network overhead.
Finally, it is inferred from the above that the time to access data mainly depends on the network io overhead.
Follow up to test and record the difference between ignite and redis, so stay tuned. If there is any error in the length, please feel free to correct it.