On Tue, Jan 04, 2000 at 09:35:01AM -0500, Mike McCauley wrote:
> Hello Paul,
>
> I would tackle this by trying things in this order:
>
> 1. Improve performance of Oracle (check your indexes, file systems, migrate to
> faster hardware, ...)
> 2. Move to a faster SQL (eg mysql)
> 3. Try a larger UDP buffer for Radiator (see the SocketQueueLength global
> parameter)
> 4. Interpose another proxy Radiator that logs to file, and have the last
> Radiator in the chain do SQL logging.
>
Or just log to file and then batch load into Oracle outside of Radiator. Using
the special formatting characters you can make a new detail file every hour,
minute or second. Of course, you get to design the error correct logic to
cope with outages and failed loads.
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
