Lowering redo generation

Hello,

I'd like to hear opinion of experienced developers regarding possibility of lowering redo log generation while keeping FORCE LOGGING on. Application needs to compute some data and the process can be restarted any time, so only the result is important. It's very space demanding, but still FORCE LOGGING should stay on for obvious reasons. There's a choice of temporary tables or doing computing outside of db but I was curious, are there more possibilities? Me, as DBA, would appreciate any experience from dev point of view.

Thanks, Michael