Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
(If this question has been discussed before, a link to that thread would be more than sufficient but I searched and could not find one.)
I am surprised that not all brokers support 64-bit (such as Velocity). As my computer supports it, it seems a waste not to use a broker that also uses it. But customer support is important to me at this point and I'm wondering what other folks thoughts are on the subject of having access to 64-bit and not availing their computer of it? TIA.
Can you help answer these questions from other members on NexusFi?
I don't understand, why 64 bits instead of 32 bits, for a data feed.
In many cases, coding in 64 bits will means more memory used, and also means manipulating bigger objects.
On a network point of view, this is the same "problem": if I want to send a single character, a 64 bits machines will transmit 8 bytes of useful information (add 64 bytes for the ethernet packet...).
I assume that a 64 bits data feed will be slower, and will consume more resources than the same one with a 32 bits API.
Ok, reality check. I work a lot of computers- also databases - inymy day to day job
* 64 prorams are larger. Memroy is a little larger when pointers are involved .Basically every poitner to an address is 62 istnstead of 32 bit.
* THis translates into a little slower execution. sSImply as less real code fits into caches.
So, no need to go 64 bit for a data connector.
THAT SAID: 32 bit is severely limtied in memory (2-3 gb, max nearly 4) while 64 bit programs can access more. THis means stuff like charting and even processing of many quotes can be more efficient in 64 bit. If you need 64 bit (and NInja can use it at times), then the price for a 32 / 64 bit bridge is higher than just putting the connector into 64 bit. Painfully high, actually.
Using 64 bit since Vista only - servers before that. And definitely not looking back
After Velocity said it was NT who didn't support 64-bit, I wrote NT, who responded, "Velocity executes through Trading Technologies. We are currently not compatible with them on the 64-bit OS. We have no ETA on when this will be."
For Ninja 32 vs 64, the only advantage is when you need to do very large optimizations: complex strategies, a lot of bars, multiples time frames and multiple instruments. In this case, Ninja will need a lot of memory, and only a Ninja 64 bits can manage more than 3 Gb.
So, unless you do this kind of things, using the 32 bits version will not change anything for you.
I don't know how Ninja is working with their data feed providers, and what information is given to Ninja by them, but I assume their give them some specifications and/or their API.
If TT API is not 64 bits, Ninja cannot do a lot against it...
