neither of those two flags are going to have any significant performance gains:

minimally logged inserts:

http://www.google.com/search?q=sql+server+trace+flag+610&rls=com.microsoft:en-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=

grow the files at once:

http://www.google.com/search?q=sqlserver+trace+flag+1117&rls=com.microsoft:en-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=

I'm skipping over the possibility of undersized hardware, memory, or slow disks as being the bottleneck for now.

well, you can start right away with query tuning;

the best thing to do would be to at least start looking at

the top 20 poorest performing queries, see if they can be changed to SARGable arguments, see if indexes would help by looking at the execution plan ;

fix the items you can identify, and repeat the process over and over again.

SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

SELECT TOP 20

CAST((qs.total_worker_time) / 1000000.0 AS DECIMAL(28,2))

AS [Total CPU time (s)]

, CAST(qs.total_worker_time * 100.0 / qs.total_elapsed_time

AS DECIMAL(28,2)) AS [% CPU]

, CAST((qs.total_elapsed_time - qs.total_worker_time)* 100.0 /

qs.total_elapsed_time AS DECIMAL(28, 2)) AS [% Waiting], qs.execution_count

, CAST((qs.total_worker_time) / 1000000.0

/ qs.execution_count AS DECIMAL(28, 2)) AS [CPU time average (s)]

, SUBSTRING (qt.text,(qs.statement_start_offset/2) + 1,

((CASE WHEN qs.statement_end_offset = -1

THEN LEN(CONVERT(NVARCHAR(MAX), qt.text)) * 2

ELSE qs.statement_end_offset

END - qs.statement_start_offset)/2) + 1) AS [Individual Query]

, qt.text AS [Parent Query]

, DB_NAME(qt.dbid) AS DatabaseName

, qp.query_plan

FROM sys.dm_exec_query_stats qs

CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) as qt

CROSS APPLY sys.dm_exec_query_plan(qs.plan_handle) qp

WHERE qs.total_elapsed_time > 0

ORDER BY [Total CPU time (s)] DESC

there's no easy way out, like a go fast button for SQL, sorry.