redis - Best way to model millions of exist checks in Aerospike? -


After going out for some data structure, I am looking at other discs with good disk / SSD display. I recently searched that seems to excel in an SSD environment

One of the most memory hungry structures is approximately 100,000 Redis sets, which can be up to 10.000 stars in each. Each string is between 10 and 30 characters.

These sets are used for existence / uniqueness testing

What will be the best way for these models? I usually see 2 options: * A model is set as a model * Separate each value individually in one set

In addition to this choice, 100.000 Redis set keys But it is possible to have a similar type of division / enrollment in the aerospeck for perhaps the reasons for the area. However, I am pretty sure that 'namespacing' concept in Aerospike is not for such kind of division. What would happen in the proper manner (if any) to do this in Aerospike, or is not it necessary?

Aerospace divides its own for load balancing and high availability requirements namespace database in traditional sense And not to split the data. The data is stored in the namespace and stored in the cluster. You do not have to worry about the placement of data as a user.

I will set a radis to aerospace "late" (one from one). Data space should be kept in mind for data in the "Let's" given to Aerospace.


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -