SQL Server 2016 in-place upgrade time for large databases Is there any statistics on how long it will take to in place upgrade SQL Server 2014 to SQL Server 2016 on a server with 1000+ databases and 10TB of storage?
How long it will take to install subsequent 2016 service packs?
Is there a way to optimize those installation times by configuration? 

The goal is to minimize maintenance windows

Update: Let me clarify a question. All production updates will be tested in QA environment, the question is not about it all.
I'm asking about known to you options to optimize upgrade duration. I'll search for those options myself by measuring upgrade time in my environment, but if there is a "previous art" - please share.
I'd really recommend not doing an in-place upgrade; certainly not for a very large system like yours.  The reasons for this recommendation are many, and have been covered extensively by Mike Walsh in his answer on a separate question.

If you really need to do an in-place upgrade, the only real way to determine the amount of time required is to do a dry run on separate, identical, hardware.  This would involve installing SQL Server, and using backup-and-restore to copy all 1,000+ databases to the test server, then performing an in-place upgrade.  I'd recommend doing this in the very minimum since it allows you to test SQL Server in your environment prior to committing to it in production.