How many items within a distributed map cache service would be considered 
excessive? I have a situation where I was considering dropping in around 200 
million, but I was thinking where the limitation (wall or performance hit) 
exists within the service.

I was thinking about using the cache service as a temporary (key / map) store 
for the duration of the entire process, and when all processing completes push 
it all to (MySQL). When I looked at my key list, I noticed it was about 150 
million keys which would have a corresponding json value to be stored in the 
map.

That got me thinking... good idea or bad one? What do you think?







Reply via email to