For many reasons I only have 3 hard drives (RAIDed and in an Always-On AG) for all my database files:
Should the tempdb log file go on F: with the data file(s) or on E:?
My tempdb data file has the highest stalls by far, with the log file 4th out of 24.
In my limited DBA experience (I'm a developer) I would lean to putting the tempdb.ldf on E: as the writes will all be sequential.
The answer here depends on a lot of things, since you are using direct disks (Local RAID) and not SAN disks which are wide striped (I assume), sequential operations are faster, so the logs (tempdb included) are benefited in E: . However there can be a situation where you don't want tempdb activity (logging activity) to interfere with the logging on your other databases, this can be the case if your tempdb activity is erratic and not related to application performance, while the logging performance of your databases is directly important to your use case.
I would generally test both setups and see which does better under the load you intend to use (the benchmarks could be transaction times for SQL Server, or disk queue lengths or writes\sec on the log drive).
In general, when not using SAN disks, it's advised to place MDF, LDF and tempdb on different drives. This will reduce I/O between them. What you can also do is to have multiple data files (MDF and NDF) for your databases, as this can improve performance
Distributing the files across different disks can be invaluable in disaster recoveries, if only one disk crashes, you have a better chance of recovery
For the tempdb, check out Microsoft's recommendations:
