Frequently Asked Questions
Tuning
Note: Differences between the Developer and Enterprise Editions are listed here.
Any tips on page pool and memory usage?
Below are some quick tips for tuning your StreamBase application. For more information on application tuning, see the Tuning Guide in StreamBase Help.
- If the page pool spikes occasionally, increase allocation in the Streambase configuration file, sbd.sbconf.
- If the page pool or memory usage continues to grow steadily, evaluate the application for resources that are claimed but not relinquished. For example, if the application never deletes entries from a memory-based query table but continues to add entries, it is inevitable that memory usage will grow.
- Every multiple stream from an output port and split operator creates a new tuple.
- Be careful to avoid infinite loops.
How do I avoid system saturation?
Consider these guidelines:
- Lock and unlock are blocking operations by design, and can considerably slow down the server. Both operations are usually unnecessary in StreamBase Version 3.0 and later.
- Try to avoid reading all rows in query table operations. Instead, consider using a secondary key with ranges, and limiting the number of output rows.
What's the best way to test performance?
StreamBase Developer Edition is a development platform. The integrated environment and graphical interfaces of the Developer Edition are ideal for application development, but it is not optimized for the measurement of raw throughput, such as the display or storage of input and output data. As a general guideline, you can expect to view input and output at a rate no greater than a few hundred tuples per second when you run applications in the Developer Edition.
If you would like to evaluate the performance of StreamBase Enterprise Edition please contact us.