|  |        hi,
        i know nothing about rtr, but have been having trouble with journal
        files.  i'm wondering how one decides how much space to allocate to
        journal files.
        our one application that uses rtr has a habit of getting hung up when
        the journal file reaches max.  allocating more blocks to the file
        worked to fix the problem in the past, but today it had to create a
        whole new journal file to get the application out of a totally hung
        up state (rtr hangs, too).
        the developers of the apllication allocated only 5k blks to the
        journal file, which doesn't seem nearly enough.  how does one know
        whether to use 5k or 200k blks?
        thanks for any pointers or suggestions,
        b-
 | 
|  | 	Different applications have different journal size requirements.
	Without knowing what your environment is it is difficult for us
	to provide any recommendations.
	For instance, these are the sorts of questions we would like answered:
	a) what is the typical kind of transaction? How many messages per
	   transaction is sent by the client?
	b) what is the typical size of these messages?
	c) how many clients do the backends serve?
	d) what is the expected transaction rate?
	e) do you expect to run shadow sites?
	f) if so, then how long do you expect a site to be running alone?
	etc...
 |