Changing all datasets to atime=off: just flip the switch?

[guermantes]

Can I simply switch datasets to atime off when they are already populated with thousands of files and snapshotting set up etc...?
Or is atime meant to be set once and for all when the dataset is created?
(Not that I am having performance problems, but why not hunt that extra possible performance boost?)

 

[Ericloewe]

You can do so at any time, but leave the top-level dataset as it is now.

 

[guermantes]

You can do so at any time, but leave the top-level dataset as it is now.

Darn... I was too trigger-happy and just before your answer came through I went ahead and switched at the top level since I figured it would be easier to have it inherited all the way down rather than changing everywhere. (I should have considered it would be safer to change only on datasets I have created myself).

1) Need I be alert for troubles to come now?
2) Should I change back at the TANK-level and make the change on my created datasets instead?

 

[Ericloewe]

I'm not sure if anything depends on atime. It's probably fine, so don't worry too much, unless something is obviously broken.