Greetings, Y'all. (Spell-checker does not object to "Y'all". Cute.)
I have a newly configured toy RH Linux system at work. When I bounced it this morning, watching the online log, the first lines were:
Parameter's user-configured value was adjusted. (DIRECT_IO)
Parameter's user-configured value was adjusted. (VPCLASS)
Parameter's user-configured value was adjusted. (DS_NONPDQ_QUERY_MEM)
It does not state what it changed from and to. (There MUST be a feature request to fill that knowledge!)
Here are those params from the $ONCONFIG:
DIRECT_IO 2
DS_NONPDQ_QUERY_MEM 51240 # Copied from prod server
VPCLASS cpu,num=1,noage
VPCLASS aio,num=3,noage
VPCLASS idsxmlvp,num=1
VPCLASS msc,num=2,noage
So I ran a simple query on sysmaster:sysconfig to get these and see what the server has done to them:
| cf_name |
cf_default |
cf_original |
cf_effective |
| DIRECT_IO |
0 |
2 |
0 |
| DS_NONPDQ_QUERY_MEM |
256 |
51240 |
51200 |
| VPCLASS |
(No default) |
idsxmlvp,num=1 |
idsxmlvp,num=1 |
| VPCLASS |
(No default) |
aio,num=3,noage |
aio,num=3 |
| VPCLASS |
(No default) |
msc,num=2,noage |
msc,num=2 |
| VPCLASS |
cpu,num=1,noage |
cpu,num=1,noage |
cpu,num=1,noage |
I see it has turned off DIRECT_IO. Could this be because the chunks are on block devices? (Linux is notoriously unfriendly to character devices.)- I also see it has removed the noage from aio and msc VP classes
Finally my main question: Why did it turn of DIRECT_IO? I mentioned block devices but is that actually the reason?
Smaller issue: Why did it turn off noage on aio and msc VPclasses?
Thanks for pointers here.
------------------------------
+-----------------------------------------------------------+
| I am pleased to report that I had no problems today. |
| I had only issues, opportunities, challenges and valuable |
| learning experiences. |
+------------------------------------------ Jacob S --------+
------------------------------