System Messages

This forum is for members of the Apiary Investment Fund. To learn more about how to get involved, sign up now or fill out the form below and preview the training right now!

Alveo on Linux.

Back to Forums

Alveo on Linux.

Hi, All,

I joined Apiary late December, 2014. I've been a Linux user since the early 90's. Since Open Source has improved so much, I've been migrating away from Microsoft for the last decade or so and this seemed like the time to really make the break. I'm most at home in the H4 period.

In a nutshell, my machine is a Quad Core, 3.4GHz AMD, 16G generic running Linux (Slackware). Alveo runs on Windows 7 installed on a Virutal Box Client. I allocate 4G of RAM to the client. W7 functions exactly, that is, PRECISELY, as if it were on dedicated hardware. Connectivity, anti-virus, updates, etc. The clipboard and drive folders share flawlessly between OS's.

So far, no issues, other than Alveo seems to develop a memory leak from time to time (Up to 800MB, more or less) and slows to a crawl. Windows crashes once or twice a month--about normal. Alveo dissappears from time to time, but I'm not sure if it's a crash or a timeout.

I use Perl (Yup, good ol' Perl) for almost all backend development. When it comes to integrating web sources with a local database, cleaning "dirty" or fixing broken quote data, building periods, etc., nothing touches Perl, IMHO, particularly at the price point. Usable, efficient modules for everything imaginable. I recently made the TA Lib ( accessable from my code with the Finance::TA module, for example.

After I send this message I'm going to write a little thing that will notify me if price movements or patterns change enough to need attention. No way perfect, of course, but I'm betting it'll keep a steady enough eye on things that I can spend more time on other things like gardening or coding.

Hopefully, by summer I'll have a VPS up and running. Coding remotely on a laptop, testing on the "big" machine.

There it is. Alveo on Linux. 

This Apiary thing is awesome. I'm having the time of my life. Very simply, I would NEVER have gotten into 4X without it.



Fri, 04/24/2015 - 11:06am

I see another kindred spirit. I also am heavily into FOSS; I have been using BSD (and other Unix variants) since 1990; I have been using Linux since 1992; and I went MS free in 1998. Thus, even the thought of having to run Windows virtualized was very unsavory.

Although I work with most major Linux distributions, I prefer use Gentoo and its derivatives (like Sabayon)--as well as Knoppix (a Debian derivative)--on my own systems. Virtual Box (which is based off an older port of Qemu) is slick, but I prefer to use Qemu instead for virtualization (for technical reasons [I'll spare everyone from the gory details]).

The requirement of using Windows--even via virtualization--was (and still is) a huge turn-off. So, unlike you, I initially opted to test running MT4 and Alveo via WINE and Mono instead. MT4 worked just fine, but Alveo wouldn't install. Alveo's installer crashed, because it called APIs linked to weakly bound symbols that aren't contained in the shipped binaries. It would be nice if the dev team were to build Alveo with options that would enable the binaries to work unmodified with Mono too--especially since VS already has built-in support for Mono targets. Doing that would make the process of getting Alveo to run natively on Linux boxes and Macs straight-forward.

I prefer to use Python instead for my development and integration. I intend to leverage MS CLR and DLL with IronPython (using Eclipse as my IDE [if feasible]) for developing scripts/EAs for Alveo. This way I can leverage various numerical packages like numpy, sciPy, pandas, sage, R, etc with Alveo for pre-/post-processing and analysis.



Kindred spirits, indeed. And with much different ways. Sounds like fun.

Thanks for all the package names, Is 'q'emu related somehow to the ancient 'Q'EMM386? The more I read the docs, the more I think there may be an etymology.

It looks like a great alternative and Ellison's procurement of vBox has left me a bit uneasy. Are the qemu RC's stable enough or would you recommend the releases?

Tried Wine and Mono also. No joy. The other packages are intriguing, particularly 'etc' :-). It'll be fun checking them out.

Looking forward to using Alveo as my data "hub", also. I sense an extraordinary discipline in the development. The platform still seems to be a bit "light" but, looking at what's been accomplished in the time frame, it seems a superbly constrained effort. Gifted developing, in my experience, no matter how heavily it may lean on MetaTrader.

Nice to meet you.

Thanks again,



Although the names are somewhat similar, I doubt that Qemu is related to QEMM386. I was a Connectix Virtual PC user for several years (since 1997), and revolted after MS acquired VPC (in 2004), and sloppily handled support during the transition. I stumbled on Qemu in my search (also in 2004) for a FOSS alternative, and haven't looked back ever since. Yet, VPC support on Macs admittedly has greatly improved since then; nevertheless, I still prefer to use Qemu and VMWare Fusion on Macs.

The real power with Qemu comes from the support for multiple CPU targets (development), virtualized hardware, nested virtualization, and clustering. :-)

I work with both the RCs and stable releases. The RCs usually are fairly stable, but it's a good idea to build client facing solutions with the stable releases. Most distros have Qemu native packages these days, but one probably should do a new build to ensure whenever working with the most recent RCs.

One could build a powerful VPS with Qemu, separating and isolating services, with fine-grain level locking (if desired). Qemu also plays well with LXC. The point is I want to contain the fallout from a potential Alveo crash. With checkpointing and load-balancing, it's not hard to setup up a VPS to soft boot, reload Alveo, and resume from where one left off (client-side) quickly. Incidentally, it would be nice to see something similar implemented server-side too.


well thats exciting! I really started getting into things when they first pentium came out p60. I used to run slackware server on that box at my house on a 768K back when that was some real speed hahah. I let all the hackers in to see if they knew anything. some did, just kids. and I Sure dont need to relive my exploits (0 day :Þ ), dont need the feds and cia fbi and dod following me around anymore.
Alveo has a memory leak alright. I also developed the energymech with Proton from Polygons old buggy spagetti code, until we disagreed about the DEV & MadCamel came along, guess he has taken it over, and I let go and they still have The script kiddies were taking our bot code and turning them into DDos bots, they spanwed, they were so wicked sitting on fat BW servers. thery networked together TCP/IP so even if they dropped from the IRC server they were on, they were still all networked together on their own private botnet. and of course any bot could be the leader and send the rest the trigger at once. Glad those days are gone heh.

I think alot about developing some trading bots, but I havent kept up with the mt4 like I used to. I guess I havent really worked in the last 20 years, I have worked a little in the last couple years after coming back to Chicago. Maybe I did do a little better at trading than I recall :P I did jump off a cliff when obama got in though and we ran down into what was that 126? I also remember getting burned a ton of times shorting GJ heading up from 225 into 251, I learned a costly lesson, dont think that stupid crap "it cant possibly go any higher" no matter how many times you say it or how hard you try to convince yourself or it, it just doesnt work!

I just got this 4G monster lenovo intel cpu box. I can see the lag on alveo now and the QS and HS, coupled to the 50Mbit cable its way faster than that old i7 laptop.