Bitcoin Forum

z

Very slow for me too.

It's usable, but it takes about 5-10 seconds for each page to load, and some more for the orderbook.

Ditto.

It's been hit or miss for me.  I was trying to access it yesterday on an Amtrak train and it wouldn't load.  This morning I got CloudFlare and nginx errors, but when I refreshed it loaded after about 10 seconds.  Not exactly the speed you need in an exchange!

Yes, I think it is getting slower lately. I think it loads a lot of unnecessary history on all pages and in an inefficient way.

Slow like hell. I've been getting intermittent errors from calling GLBSE trade data through the API.

lot of people running trade bots maybe

Every time I view the Markets page, the 30-day history column is filled with the actual data from the 30-day history, and the graph loads seconds later. Perhaps this is a contributing factor, especially as it happens for every security on the page.

If it gets any slower, the use of pigeons might be handy  ;D

GLBSE wins award of the slowest site of the year.  

My only hope their security is much much better handled than their data rendering processes

Yes, very slow. And from what I understand bitcointalk.org is owned by glbse and I am also experiencing very slow load for bitcointalk.org.

I know I've stated this before in meta and was explained to me that it won't help the forums, but do you think adding SPDY to glbse would help?

http://en.wikipedia.org/wiki/SPDY

https://bitcointalk.org/index.php?action=;topic=79278.0

My spdy indicator does not notify me that glbse has implemented spdy.

I still think spdy would help the forum and glbss.

Edit:

That is funny as heck.

Yeah, really slow... and because it's using TOTP it makes trying to use the GA 2FA an exercise in frustration.  Nefario really should have  gone with HOTP. :(

Before offering solution, root cause of problem needs to be identified first.
IMO in case of GLBSE it has very little to do with connectivity and everything to do with database querying since their load have increased recently with traffic, DB is taking major hit.  Few month ago it was flying with little to no traffic.

Certainly not me, of course... *cough cough* ::)

Ditto!

I have no idea why you would think that, but it is completely untrue.

Ok, I was wrong, MT.GOX owns it. scratch my entire post.

Nah, must be pirate who owns it  ;)

This is also untrue.

omg, ugh, who owns bitcointalk.org?

I looked at a post that sirius passed it on to mt.gox, was bitcointalk.org just recently passed to a new owner?

The company behind MtGox (tibanne) actually owns the infrastructure used to host this very forum here afaik. The forum itself is independent.

Back to GLBSE though I fear they have hit another wall - maybe not enough RAM? The problem is that caching is not really an option as most of the data is expected to be live. I already had a problem where I bough some shares by setting a bid slightly below the highest ask at that time and in the meantime somebody must have placed yet another ask... if this would have been because of caching and not my slow typing skills, I'd be pissed a bit.

Also I looked at the fees I have paid on GLBSE 2.0 so far - less than 1 BTC with pirate for 2 weeks. Is there some way for us to donate shares and/or BTC to GLBSE? Ideally there would be a public wish list + you can vote by sending some BTC to an address written next to the feature.

if GLBSE is short on operating capital they could raise it through their own platform

Seriously, let us all own it.  Stock SALE!!!!!

For me GLBSE effectively became not usable over the last two days. My laptop needs about 40 seconds to load the asset page, while id does not even load any more on my mobile device (where I am mostly limited to over the day). I got recently even used to fire the button 20 seconds early to assure my dividend payments get executed at the exact minute of the due time.

Looking at the source code of the asset page got me scared somewhat: it contains the complete price history of any security and renders the charts in JavaScript -- every time a user reloads the page  :o No wonder my mobile hangs there, it most probably runs out of mem when plotting the 100+xth chart.

Aside from being inefficient and problematic for mobiles, all-time charts are not really helpful on the asset's frontpage. If at all, they should span all a common time frame for comparability (say 30 days). This would allow to generate them once a day as graphics for embedding. With the right cache tags every user would have to download them only once a day. Pre-rendering of charts would definitely also improve usability of the securities' detail pages - let's hope this is all in the way for GLBSE 3.0.

I'd personally love to invest, but I believe that's against Nefario's policy of not being involved in assets other than for testing.

pages are taking 8-10 secs to load up for me.

My big problem is if you don't time entering your google auth key in with enough time left on the timer, it will time out the saying the key is wrong because it expired while it was trying to load the webpage.

So slow, I'd have to call it laggardly.

I just ate dinner while entering a new security.

Like this?

https://i.imgur.com/Lqa3p.png (http://imgur.com/Lqa3p)

I counted 190 bids for a total of 212 coins. Tradebot fail.

"Hypothetically" what would you value GLBSE at ? And what do you think the price per share would be ?

 :)

Nefario is away and experiencing connection issues so Ive heard.

And that was a "squatted" asset.

Also it was heavily overpaid... I'd have to check it out again, but I think a realistic price for one GLBSE share would be something around a few bitcents.

7 9 confirmations and no sign of my coins :/ there now

He needs to protect the existing GLBSE shareholders. No one likes their ownership getting diluted as you can imagine.

I wonder who setup the asset....

Regarding the GLBSE shares, they are not publicly traded, and this has always been our position(although we failed to prevent trading initially, we did eventually lock it down).

Goat bought shares which were fraudulent without checking if they were genuine or not, a lack of due diligence. As a gesture to the small number of users who were hit by this scam (of which Goat was one) we decided to honor them. As Goat has said he's profited off this quite a lot and I really don't see why he's complaining.
 
Regarding performance, there are two issues:

First is the exponential growth of new users and the number of users on GLBSE at any one time, this is obviously contributing to the slowness.

Second, GLBSE is being hammered by bots, I mean HAMMERED, which is slowing everything down for everyone.

There is a two pronged approach being taken to this, the first being to get the API onto a single application server, so when the bots get active it won't affect normal users. The second will be to add more application servers in general.

Both steps require coding and testing before being rolled out.

I'm working on it with a view to have the issue solved by Sunday at the latest.

Nefario.

On the plus side, this growth, which is slowing th site down is a good thing for everyone involved.

Nefario.

+1

Thanks for your work Nefario

I assumed you'd bought at the beginning, I don't look at peoples accounts unless they ask(usually if they have a problem), much more interesting and important things to do.

The ones who got scammed are the glbse shareholders as they are the ones who have to cover the loss of a scam asset I would imagine :)

What are you talking about, when did I go back on my word?

Payouts seem to work slow as well :(

I understand GLBSE can't keep it all @ hotwallet - but after 20 hours of waiting, i really don't know if a technical error accured or if it just needs some more time ^^

It IS valid, it's not publicly traded, this means that shares should not be bought or sold on the exchange.

As I said before I don't keep track of peoples trading(we do have records of course) and so ASSUMED you bought when the asset was first released. Wrong assumption.

Is anyone else getting to a point where the speed is negatively effecting there usage of the website and thinking about switching to API only or switching exchanges completely?

Every task is taking 10+ secs and I find myself not doing trades because of the amount of time required to do what I want to do.

I'm worried he is sacrificing the performance of the site and the "user experience" by allowing the use of the API right now.

I know the big guy is behind the great firewall right now, but this really needs to be addressed with a timeline of possible fixes.

Also I really hope someone has told the big guy about current security SOP for bringing laptops and phone in and out of china.

Why not just turn off the bots until the next update gets done?

Also, has anyone had any issues with the javascript captcha? I have all the latest Javascript installed and enabled with three different browsers but I still get a message from GLBSE that 'Javascript is needed to view captcha'. Very annoying not being able to login.

I would also like some kind of throttle (not more than 1 page loaded or 10 API requests per second or whatever other limit could be useful) until the server GLBSE runs on has been upgraded.

Im sure a fix for the slowness of the site is coming soon. Just hang in there awhile longer guys  :)

I have to click and go do something else and come back later to see if it accepted my request to do something or see another page. This can't be caused by legitimate usage of the current userbase, it is constant and way beyond what a few thousand people should be causing. I'm a total noob, but I think it's loading up and even calculating data that it doesn't need to on every page load. Why does it flash me a huge list of previous trades(?) all the time and then not even show that after the load is finished?

I hope it gets fixed soon, I don't see an alternative.

GLSBE might want to build their own internal caching mechanism for individual asset pages.  data is almost static there, it doesn't change much, and when it does just save it into output html format kind of snapshot and serve that instead rather than pulling same data all the time from db on every request.


i would also recommend thoroughly optimizing code-base and processes, get rid off all extra db queries for each particular page/view before expanding hardware

Curious about this.. what is the current security SOP for bringing laptops and phones in and out of china?

He's been in and out a few times, so should have it down I'd think.

Don't bring any laptop or phone that has or had any trade secrets or anything of value on it.
Most current SOP is to only use laptop and phones purchased for the purpose of taking to china(IE CLEAN), after coming back getting rid of them.

there have so many reports of people coming back with NEW firmware IE(RootKits) and other great software add-on's.

Its a current industry theory that if someone in customs takes your laptop out of your view your already infected.

Just saw a nice stat today saying that china has backdoor access to 80% of the worlds telephone systems now thanks to two big Chinese telecom companies.

Anyone hear about the plotter(Big Printer) that had its software changed so it forwarded all blueprints that it printed out to china.

 ;D

Next time I go I'm taking an ultrabook with all the ports epoxied shut with a drive encrypted with AES-Twofish-Serpent.
After you start raising flags at customs, we get a special detail that follows you the entire trip.
Then you start doing fun stuff like talking to trash can's,dead dropping dollar bills at random places with special codes, watching the aftermath is always fun.

http://blog.glbse.com/no-electronic-devices this didnt happen in china  :P....

If GLBSE login takes more than 20--25 secs the login fails do to using google otp which has a 30 sec timer to expire the codes.

If the page load time continue to increase after they hit ~25 secs, I will no longer be able to login.  >:(

Im workin on it, Im workin on it.

Really the problem is programmatic, I can't just throw hardware at it.

The way to fix this is to add application servers (currently only one running), but this add a concurrency problem which under heavy load would mean that accounts wouldn't balance, there would be double trades etc.

I'm working on making this safe and scalable.

Interesting.. it sounds tinfoil hat, but it probably isn't :/

Well, they need to catch up to the USA after all! ;)

Please Nefario, choke bots in the meantime or take down some heavy stuff that is not 100% needed - it is really not fun at all to not know whether your order went through or not or to sell into a suddenly appearing bidwall instead of placing an open order.

GLBSE has been having these issues since v2.0 launch  and the Google OTP has just made it worst, as I usually need to type my OTP two or more times before it works and make sure I type it as soon as it recycles to a new one. Then you get to the re-captcha screen which is even more of a pain in the ass.

Unfortunately i'm a small time investor so I'm selling all of my GLBSE assets and buggering the hell out. Mining is moving downwards (at least for the next few months 'til we have a more clear picture with ASICs and stuff), GLBSE is not capable of scaling all that gracefully so I've decided to buy a used old netbook, install Ubuntu and Armory, liquidate all of my assets, including my GPUs and workstations, put all my coins in that laptop and wait it out.

Yea I'm probably going to lose some potential profit in the process but better safe than sorry.

You shoulda tried webkeys if you think thats annoying :)

Can you simply disable the graphs for a while?  The pages are loading every trade since asset launch and the data is becoming very large.

The bids/asks graph in particular should be disabled if it would improve anything.

+1

This is exactly why I advised to use HOTP and not TOTP in the beginning.  It's just a monumental pain in the ass... please add an HOTP option in addition to TOPT if you are unwilling to ditch TOPT completely.

I have to stop scripts every time i visit. Thanks for working on it nefario.

No exactly true, we've had periods where things were slow (right after 2.0 launch, and then about a month later as system load picked up) but we've generally sorted this out after one or two weeks.

Performance improvements will be here in the next two days with numerous other usability improvements to follow very soon after.

Nefario.

Kick all those damn bots! This will speed things up considerably and probably makes market more stable. Fuck those few share asshole bot runners and their bots.

Bots are people too  :)

+1 for an HOTP option! :)