I believe the log file is seeing that large size because during the backup from production the size there itself was 3.6 GB approx.
As mentioned below by experts, excluding the part of my answer recommending a fix size. Therefore,to analyse more on how to decide the size you may want to keep, check on the autogrow size of data and log file:
select DB_NAME(files.database_id) database_name, files.name logical_name,
CONVERT (numeric (15,2) , (convert(numeric, size) * 8192)/1048576) [file_size (MB)],
[next_auto_growth_size (MB)] = case is_percent_growth
when 1 then CONVERT(numeric(18,2), (((convert(numeric, size)*growth)/100)*8)/1024)
when 0 then CONVERT(numeric(18,2), (convert(numeric, growth)*8)/1024)
end,
is_read_only = case is_read_only
when 1 then 'Yes'
when 0 then 'No'
end,
is_percent_growth = case is_percent_growth
when 1 then 'Yes'
when 0 then 'No'
end,
physical_name
from sys.master_files files
where files.type in (0,1)
and files.growth != 0
Also It is not recommended to keep “In Percent” File Growth option for database files. If “In Percent” option is used for any database file and if the file size is very big, it may cause performance degradation during the file growth phase.