|
PureBytes Links
Trading Reference Links
|
<SPAN
class=940505719-23062003>Ken,
I keep
2 databases one for EOD data and one for 1 min data. During the day I switch my
EOD data from the QP plug in to the Esignal plug in. This means that during the
day my EOD data is current to LAST NIGHT except for the charts I have open
today. I ran the update with "wait for back fill" on a db of roughly 1000 +
stocks and it took around 25 minutes. This is a far cry from the numbers you are
reporting. My conclusion (and one you can verify tomorrow) is that once your DB
is current (or nearly current) that the update speed will be dramatically
improved for you as you will only be updating 1 days missing
bars
Regards,
Jayson
<FONT face=Tahoma
size=2>-----Original Message-----From: Ken Close
[mailto:closeks@xxxxxxxx]Sent: Monday, June 23, 2003 3:43
PMTo: amibroker@xxxxxxxxxxxxxxxSubject: RE: [amibroker]
eSignal Not Connecting
<SPAN
>Hi Rick: yep, I
did that this morning about a dozen times (in addition to shutting down AB and
restarting). It stayed $B!H(Blocked out$B!I(B until I restarted my computer (even
thou I had just started the computer for the day about 10 minutes prior to the
attempt to get the plugin connected).
<SPAN
>
<SPAN
>Have you (or Jayson)
tried a complete update of your RT database with the $B!H(BWait for Backfill$B!I(B
checked? I reported in a previous message how it took 6 to 8 hours
to update 1050 tickers and then 15 minutes to save. Tomasz provided some
statistics that said that was not so bad a time. My $B!H(Bguess$B!I(B is that
something associated with the update and subsequent save $B!H(Bdid something$B!I(B that
made the plugin lockup on startup this morning, which the subsequent restart
unlocked. But, who knows$B!D(B
<SPAN
>
<SPAN
>Ken
<SPAN
>
<SPAN
>PS: I just
recalled that Tomasz said one of the things I could do in order to not have
memory problems is to reduce my $B!H(Bin-memory cache$B!I(B. I just looked and even
thou my database only has 1050 (+/-) symbols in it, I see that I have 6657
(symbols) in the in-memory cache box. I am not sure when or why such a
large number got there, but I will reduce it and see what happens. I am
still maintaining 100,000 bars to load, which is only about 1 year$B!G(Bs worth of 1
min bars.
<SPAN
>
<SPAN
>-----Original
Message-----From: Rick Parsons
[mailto:RickParsons@xxxxxxxxxxxxxxx] <SPAN
>Sent: Monday, June 23, 2003 2:37
PMTo:
amibroker@xxxxxxxxxxxxxxx<SPAN
>Subject: RE: [amibroker] eSignal Not
Connecting
<SPAN
>
<SPAN
>Ken,
<SPAN
>
<SPAN
>I have not upgraded to the new plugin yet
but still get WAIT status. I find right clicking on the WAIT status and
selecting SHUTDOWN then right clicking on WAIT again and selecting CONNECT
sometimes wakes up the plugin and sets the state back to
OK.
<SPAN
>
<FONT color=navy face="Vladimir Script"
size=5><SPAN
>Rick
<SPAN
>-----Original
Message-----From: Ken Close
[mailto:closeks@xxxxxxxx]<SPAN
>Sent: Monday, June 23, 2003 10:21
AMTo: AmiBroker
ListCc: 'Tomasz
Janeczko'Subject:
[amibroker] eSignal Not Connecting
<SPAN
>Is anyone else having trouble with the new eSignal
plugin connecting to<SPAN
><FONT
face="Courier New">all of the servers.<FONT
face="Courier New">The attached shows the eSignal application displaying
current RT datawhile right beside
it, the AB RT application is still waiting to<FONT
face="Courier New">connect.<FONT
face="Courier New">Since the new wait for backfill capability was issued on
Saturday, Isuspect there is a bug
of some sort in the eSignal dll.<FONT
face="Courier New">Comment?<FONT
face="Courier New">Ken<FONT
face="Courier New" size=2>Send BUG REPORTS to
bugs@xxxxxxxxxxxxx<SPAN
><FONT
face="Courier New">Send SUGGESTIONS to
suggest@xxxxxxxxxxxxx<FONT
face="Courier New">-----------------------------------------<FONT
face="Courier New">Post AmiQuote-related messages ONLY to:
amiquote@xxxxxxxxxxxxxxx (Web
page: <A
href="">http://groups.yahoo.com/group/amiquote/messages/)<FONT
face="Courier New">--------------------------------------------<FONT
face="Courier New">Check group FAQ at: <A
href="">http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your
use of Yahoo! Groups is subject to the <A
href="">Yahoo! Terms of
Service.
<SPAN
><FONT
face="Courier New" size=2>Send BUG REPORTS to
bugs@xxxxxxxxxxxxx<SPAN
><FONT
face="Courier New">Send SUGGESTIONS to
suggest@xxxxxxxxxxxxx<FONT
face="Courier New">-----------------------------------------<FONT
face="Courier New">Post AmiQuote-related messages ONLY to:
amiquote@xxxxxxxxxxxxxxx (Web page:
<A
href="">http://groups.yahoo.com/group/amiquote/messages/)<FONT
face="Courier New">--------------------------------------------<FONT
face="Courier New">Check group FAQ at: <A
href="">http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your
use of Yahoo! Groups is subject to the <A
href="">Yahoo! Terms of
Service.
Send
BUG REPORTS to bugs@xxxxxxxxxxxxxSend SUGGESTIONS to
suggest@xxxxxxxxxxxxx-----------------------------------------Post
AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx (Web page: <A
href="">http://groups.yahoo.com/group/amiquote/messages/)--------------------------------------------Check
group FAQ at: <A
href="">http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to the <A
href="">Yahoo! Terms of Service.
Yahoo! Groups Sponsor
Send BUG REPORTS to bugs@xxxxxxxxxxxxx
Send SUGGESTIONS to suggest@xxxxxxxxxxxxx
-----------------------------------------
Post AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx
(Web page: http://groups.yahoo.com/group/amiquote/messages/)
--------------------------------------------
Check group FAQ at: http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|