Here are the results. Looks like quite a difference from the intital settings.
tempdb templog initial_size_MB actual_size_MB auto_grow_setting change_in_MB_since_restart
8.00 541.31 10% 533.31
0.50 74.94 10% 74.44
Thanks for posting back. That's actually not too terrible. Your last data file autogrow was by ~50MB which can take several seconds on a slow and overloaded I/O subsystem if instant initialization is not enabled, however hopefully not so overloaded as to approach a common timeout periods of 30 seconds. That said, I think you will want to start thinking about adjusting your initial tempdb file sizes since chances are very good that your instance needs additional space over 8MB for data and .5MB for log. For autogrow, personally I prefer to have my files grow by MB and not by percent because growth activity is more predictable in terms of how long it will take and how large the file may grow if a runaway process happens to crop up.
Chances are you can still see when your files autogrew, buy how many megabytes and how long each autogrow operation took by looking in the default trace. The default trace is a sliding window of activity but chances are your most recent autogrow events will still be there. See the article by Aaron Bertrand in the References section of the article for how to read the default trace looking for autogrow events.
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato