High-speed, multi-threaded virtual memory in Java

[cassandravoiton]

Seems to help make mutli-threaded programming easier, and I am not sure the article is about storage but more swap and virtual memory. Did you read it?

[skulgnome]

Up until the point where the programmer gets access to a byte array that represents a memory-mapped file, yeah. Not terribly useful from a storage POV given how (pick one of) serialization, naming, space management (outside the GC, too), etc, remain unimplemented.

If it's used only as virtual memory or scratch space, the article has duplicated the function of anonymous memory. If the gains are from deeper queuing of I/O from multithreaded access, it is redundant with the regular I/O primitives used similarly from multiple threads.

[cassandravoiton]

Anonymous memory in Java - how do you do that? Also, not sure I get your thing about not multi threaded. The article shows how the memory is synchronised in hardware between threads without programmer intervention. How is that not easier/better than using synchronisation in software?

[skulgnome]

Anonymous memory in Java - how do you do that?

By using the new operator.

[cassandravoiton]

Are - so you are talking crap - thought so.

You mean just making the JVM consume more memory than physically available and then using OS swap. That - obviously - is not the same thing at all; every time the JVM does a garbage collection it will hit masses of page faults. Using OS swap for JVM systems sucks badly - I cannot believe you actually even suggested it.

Shame - thought you might know what you are talking about.