For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
Might It can be silly question. But in my system today I deleted all redo log file and still I was able to do commit record.
Can anyone tell me how it happened.
Hi,
Your Zone now has 16GB of RAM. Please let me know if that is sufficient
-Angelo
Thank you. Now memory limit is sufficient.
But CPU offloading still shows that while DAX doing its work - CPU core busy too.
With new memory limit vector_in_range() takes 0,8 seconds to complete. Let's run it in cycle on the same thread id with "yes > /dev/null" (using pbind). Again, we see that yes shares CPU time with dax-in-range:
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWP
19860 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19868 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19864 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19866 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19857 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19862 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19870 dglushe* 99 1.0 0.0 0.0 0.0 0.0 0.0 0.0 0 30 34K 0 yes/1
19880 dglushe* 50 15 0.1 0.0 0.0 0.0 0.0 35 1 23 .1M 0 dax-in-range/1
19850 dglushe* 34 0.3 0.0 0.0 0.0 0.0 0.0 65 0 24 10K 0 yes/1
Oh, I see you shared dax.h. It seems that vector.so uses synchronous DAX calls, but dax.h states that there are asynchronous calls too:
/* NAME: dax_post - family of functions that post asynchronous dax requests SYNOPSIS: */ ..
/*
NAME: dax_post - family of functions that post asynchronous dax requests
SYNOPSIS:
*/
..
No more questions, thank you!