A VLDB contest
Also, when your server process needs metadata for an
ASM allocation unit which is not already cached in your databases memory, it
needs to do an OCI call to ASM instance. This in turn will make an IPC call
to ASM instance, possibly spawning a new ASM process.
And then ASM instance will read the metadata from disk, and
pass it pack to the waiting server process, then the server process has to get
onto CPU again to continue processing (for example loading rows into a table) -
once it requires a next ASM allocation unit for itself...
Also, no FUD intended here. The few small to medium
databases what I've (had to) set up with ASM have performed
Right, the ASM instance gives the pointer array info
consumer instances where it is cached in the shared
I've not seen one iota of discussion on this list
Oracle maps a data block to an extent within an ASM
Must not be an interesting topic?
It is indeed using these pointers. Such mapping is
never free. Volume
managers have always had to do that--but have always
such mappings in kernel memory. No FUD intended here.
wanted to get people curious about the topic.