dunit | Test code against multiple versions | Unit Testing library

Geode's internal testing framework does this in several places, actually, I'd suggest having a look at the geode-dunit project for examples, specially at the Blackboard java class. Cheers.

malloc is implemented via HeapAlloc which is implemented in system function named RtlAllocateHeap.

The function manages heap. It allocates system memory pages via VirtualAlloc[Ex] or its equivalent, and provides smaller allocations within these pages.

With larger allocations, the VirtualAlloc[Ex] equivalent is called on every allocation, with smaller allocations it is called occasionally.

VirtualAlloc[Ex] is implemented using NtAllocateVirtualMemory which is kernel call. Most of the time spent in it is not counted in lpUserTime.

On the other hand, QueryPerformanceCounter is a honest total time.

The first problem that i met is that Cache cache = CacheFactory.getAnyInstance(); should not be executed in constructor. In case it is , the code is executed in client instance , it is failed on not server error.When this fixed i receive

Once the Function is registered on server side, you can execute it by ID instead of sending the object across the wire (so you won't need to instantiate the function on the client), in which case you'll also avoid the Serialization filter error. As an example, FunctionService.onServers(instance).execute(CreateRegionFunction.ID).

The problem is that code is getting executed on dunit MemberVM and the required class is actually the part of the package under which the test is getting executed. So i guess i should somehow register the classes ( or may be jar ) separately to dunit MemberVM. How it can be done?

Indeed, for security reasons Geode doesn't allow serializing / deserializing arbitrary classes. Internal Geode distributed tests use the MemberVM and set a special property (serializable-object-filter) to circumvent this problem. Here's an example of how you can achieve that within your own tests.

Another question is: currently the code is checking if the region exists and if not it calls the method. In both cases it also tries to create the clientRegion. The question is whether this is a correct approach?

If the dynamically created region is used by the client application then yes, you should create it, otherwise you won't be able to use it.

As a side note, there's a lot of internal logic implemented by Geode when creating a Region so I wouldn't advice to dynamically create regions on your own. Instead, it would be advisable to use the gfsh create region command directly, or look at how it works internally (see here) and try to re-use that.