hi guys, any security concerns over the TWS login info; and the code being deployed in the hosted services?
cheers. issy On Aug 1, 2:11 am, Eugene Kononov <[email protected]> wrote: > Thanks, Judson. I have a question about the EC2 micro, since you used it. > What would you use to run GUI based apps such as TWSGateway and JBT on a > Linux micro EC2 instance remotely? > > On Sun, Jul 31, 2011 at 1:57 PM, Judson Wilson <[email protected]>wrote: > > > I've played with micro in different contexts, and I was not impressed. I > > would not use it. It goes from fast to VERY slow over different periods of > > time. > > > I did compare small for 24 hours a day, I think, a while ago, and it just > > didn't make sense. Maybe it does now. I am too lazy right now to wake up > > at like 3AM to turn it on in the morning. > > > 256megs of ram is enough, no problems there, so long as you are running one > > single instance of JBT from the command line (not from within eclipse). > > > Back when I did the math, linode was the best choice. > > > On Sun, Jul 31, 2011 at 9:27 AM, Eugene Kononov > > <[email protected]>wrote: > > >>> .. and it seems the micro instance should be enough (with Linux) 613MB > >>> RAM. It is only unclear what bursts of CPU means and > >>> what their standard is (i.e., continuous CPU usage ok?) > > >> Yes, 613MB RAM should be enough. You can confirm it experimentally by > >> running JBT in the trading or forward testing modes with this options: > >> -Xms512M -Xmx512M. In regards to the CPU usage, JBT consumes very little, > >> unless it's running the optimizer. The only possible issue withe "micro" > >> instance is that it lists the I/O performance as "low", compared to the > >> "moderate" for the small instance. If the "I/O" refers to the disk I/O, we > >> don't care, as JBT uses very little of that. However, if this refers to the > >> network throughput, it could mean that the latency may be more significant > >> with the "micro" instance. > >> * > >> Micro Instance* 613 MB memory > >> Up to 2 EC2 Compute Units (for short periodic bursts) > >> EBS storage only > >> 32-bit or 64-bit platform > >> I/O Performance: Low > >> API name: t1.micro > >> * > >> Small Instance* > > >> 1.7 GB memory > >> 1 EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit) > >> 160 GB instance storage > >> 32-bit platform > >> I/O Performance: Moderate > >> API name: m1.small > > >> I'll probably sign up for the "micro" instance, and see how it goes. > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "JBookTrader" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >>http://groups.google.com/group/jbooktrader?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "JBookTrader" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/jbooktrader?hl=en. -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
