To see how many VLFs you have solely look at the number of rows returned by DBCC LOGINFO.
The size and number of VLFs you’ll have depends largely on the size that the chunk is when it’s added to you transaction log.
There is no general rule how to determine the best values for the auto-growth option, as these vary from case to case. Having too many or too little virtual log files causes bad performance.
Having an excessive number of VLFs can negatively impact all transaction log related activities and you may even see degradation in performance when transaction log backups occur.
Most of the time excessive VLF fragmentation is brought about by excessive file growth at small intervals. For example, a database that is set to grow a transaction log file by 5mb at a time is going to have a large number of VLFs should the log decide to grow.
|Growth||Number of VLFs created|
|>64 but <=1Gb||8|