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)
NexusFi site changelog and issues/problem reporting
Two changes to report. I'm only mentioning these specifics for those technical enough to care
One, futures.io (formerly BMT) is now serving files through a CDN (content distribution network) where possible. There are about a dozen datacenters worldwide in the CDN, so there should be one near you (closer than Chicago for vast majority of you). The net result is pages will load faster. I'll be continuing to tweak it in the coming weeks and months, there is still room for improvement but I have to hire some more work done by our developer to get more efficiency for now. The moderators report about a 2-4x improvement in latency (ping times) with this change.
Two, bmcharts.com is now running off our new cluster config. It's serving as an intermediate test before we migrate futures.io (formerly BMT) to the new cluster.
On the bottom right hand corner of the bmcharts footer, you'll see "lb1" or "lb2" and "app1" or "app2". This tells you which load balancer/proxy cacher you came in from (lb1 or lb2), and then which application server processed your request (app1 or app2). There are also db1 and db2 for the databases, but that info isn't reported on the page.
This info will eventually be reported on the footer of forum pages as well, after we complete the migration. If you look at the footer of a futures.io (formerly BMT) page right now you'll see just the first part "lb1" or "lb2", as we haven't finished migrating everything yet for futures.io (formerly BMT).
Most web browsers will "lock on" to a particular load balancer (DNS A record) for an entire session, and will only change if there is a problem with it. But you'll see the application server change back and forth as you flip through pages.
The transition should be seamless, but please report any problems. The change was brought on by our datacenters hardware problems that I've been unhappy about, and since I was going to move the server I wanted to do it in a cluster to make things more modular, add redundancy, and scalability.
Thursday evening our old datacenter had an outage again. So, I decided to go ahead and make it a priority to move futures.io (formerly BMT) to the new cluster.
futures.io (formerly BMT) was down about 2 hours this morning (1:00am ET to 3:00am ET) while I did this.
There are still some problems, however. The site is running slow because I've had to disable all the caching, and I need some time to track down what the issue is.
But, everything else should be functioning, so if you see any problem please report it here. When you report it, please try to tell me which lb and app server you were on (at very bottom of page, it will show lb<x> and app<x> next to the page generation stats).
If you are wondering what happened to the "Unread posts: xx (list, clear)" at the top right of every page under your user name --- I removed it.
I've been focused on improving the performance/speed of the site, and I recently discovered this addon was a performance killer. Big time. So, it is gone.
Please use the "New Posts" menu item off the navbar instead.
If you want to "clear" unread threads (reset to zero new posts), you'll need to use the Mark Forum Read option under the Quick Link menu now.
I think that change caused a bug... IE is indicating a scripting error now when the 'New Posts' page is loaded, and the 'new' tag isn't being removed from posts on the list when you use 'back' to return to that page after reading a post, as it used to be.
Thanks for reporting. Actually, it is not related to the new posts I removed, although the timing and content would seem so. Instead, it seems to be an issue after I upgraded the Wiki from 3.0.3 to 3.0.4. I've opened a ticket with the developer as I couldn't figure out what the problem is at first glance.
