Sorry, I didn't phrase that well. Generally for databases under 1 terabyte, you don't want to have hundreds of VLFs. There's no hard guideline for the exact number, suggest reading the SQLSkills link and its associated links for better advice. For the data size you have (just data, not including the log), I'd say you want to resize your transaction log to something smaller, maybe 32, 48, or 64 GB. BUT, you want to shrink the log and then resize it so that you end up with about 100 or so VLFs.
Here's an example script:
use myDB
dbcc shrinkfile(2); -- want to shrink file to absolute smallest size possible
alter database myDB MODIFY FILE(name=logname, filesize=2GB) -- this will create 8 VLFs of equal size
alter database myDB MODIFY FILE(name=logname, filesize=4GB) -- this will create 8 more VLFs of equal size, adding 2 GB
alter database myDB MODIFY FILE(name=logname, filesize=6GB) -- this will create 8 more VLFs of equal size, adding 2 GB
... -- additional file resizing in 2 GB increments
alter database myDB MODIFY FILE(name=logname, filesize=32GB) -- this will create 8 more VLFs of equal size, adding 2 GB
The "..." placeholder section, you'd add commands to increase the log file size by 2 GB until you get to the final size, in this example, 32 GB. Note that this is NOT the same thing as setting a file growth increment, it's increasing the size of the file in fixed increments in order to create the final number of VLFs that you want. You also want to have the VLFs be the same exact size as best as you can, so you always want to increase the size with the same increment each time.