M
Marcelo Pacheco
Guest
The beauty of memory mapped pls is we use OS features to handle concurrency. We're simply avoiding reading pieces of the .pl into private buffers. We just map pieces of the .pl file corresponding to r-code segments and point directly to those mapped buffers. It should follow that if performance is good with few users and bad with lots of users, the OS / OS tuning is at fault. I suggest taking a deep hard look at the mmap(2) system call page. There are no latches/locks or any type of contention visible from inside the OE client. It simply doesn't know if it's alone using the .pl of if a million people are using it at the same time. Marcelo Pacheco
Continue reading...
Continue reading...