GPP Drive map and logon impact

Hello,

GPP drive mapping requires synchronous processing which cause slower logon time. But it seems after reading this article here http://blogs.technet.com/b/grouppolicy/archive/2013/05/23/group-policy-and-logon-impact.aspx  that if you don't modify the GPP drive mapping after it has been applied, for every other logon, policies will be process asynchronously resulting faster logon. This is not what I experiment, even if I don't modify the GPP, every two logon, policies are process synchronously

Here another way to improve logon time when using GPP drive map :

http://social.technet.microsoft.com/wiki/contents/articles/12221.troubleshooting-the-drive-maps-preference-extension-in-group-policy-replace-mode-only-maps-the-drive-every-other-logon.aspx?wa=wsignin1.0 :

... The reconnect option is the same as mapping a drive using the /PERSISTENT attribute. This allows the state of the mapped drive to be saved between user logon sessions.  In this solution, use Create action to map a drive that persists between user logons. This would allow for faster logons because Group Policy wouldn’t be forced to run synchronously every logon cycle.

Same here, even if I set the persistence attribute, every two logon, policies are processed synchronously.

Are those both articles given wrong information or do I miss something?

Thank you for your help.

Chris