Re: [luciddb-users] [RESOLVED] Problem Recognizing UDX AtPrepareTime

[Julian H. <jul...@sq...>]

OK, good to hear. SQLstream only goes fast if you give it data!
 
Julian


  _____  

From: Nicholas Whitehead [mailto:nwh...@he...] 
Sent: Wednesday, July 01, 2009 2:37 AM
To: Julian Hyde
Cc: luc...@li...
Subject: Re: [luciddb-users] [RESOLVED] Problem Recognizing UDX
AtPrepareTime


Uh.... yes,I should qualify that. 
SQLstream is not running flat out, but I am able to save whatever it sends
without getting backlogged.
What Lucid is actually outpacing is my event sender as my load test is
pretty much a "straight pass through" for SQLstream.

Sender --> SQLstream --> LucidDb

Cheers.

//Nicholas



On Tue, Jun 30, 2009 at 7:00 PM, Julian Hyde <jul...@sq...>
wrote:


 


  _____  

Nicholas Whitehead  wrote:

The streaming interface works really well now, although it does use some
"creative" techniques to get data from my stream mediator to the UDX. At the
very least, I cannot get SQLStream to kick out messages faster than I can
save them in LucidDb, so I remain ahead of the game.

I'm a bit surprised/disappointed at that. Usually we find that SQLstream can
generate data faster than it can be written to disk. (Even given LucidDB's
impressive load speed.) We should look into that.
 
A couple of possible explanations spring to mind: Are you perhaps running
SQLstream on the same box as LucidDB (in which case LucidDB's writer threads
are starving SQLstream of CPU cycles); or are you running some expensive
transforms or user-defined functions in SQLstream?
 

Julian