Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: 0.5.1 and 0.5.3 are unusable for me  (Read 875 times)

0 Members and 1 Guest are viewing this topic.

Offline arhag

  • Hero Member
  • *****
  • Posts: 1213
    • View Profile
    • My posts on Steem
  • BTS: arhag
  • GitHub: arhag
0.5.1 and 0.5.3 are unusable for me
« on: January 24, 2015, 03:33:38 AM »

I have tried both building 0.5.3 myself and using the pre-compiled 0.5.1 binaries. The results are the same: the clients are totally unusable.

The CLI client of both versions still has the unbearable typing lag I mentioned last time. Running it with --server and using the web wallet doesn't help. It is very slow. The RPC POST requests have an average latency of around 2 minutes and some of them timeout with an error!

The Qt client isn't better. The 0.5.3 Qt client is very slow and laggy and sometimes won't ever load pages like the market. In fact it completely froze my Ubuntu system (hard reset required) when I tried to load the market in an attempt to cover a short! The performance of the 0.5.1 Qt client was actually pretty decent, but I quickly realized the only reason that was the case was because the blockchain wasn't syncing at all beyond the point left by the CLI client (a problem I mentioned last time with v0.4.27.2), meaning its completely worthless.

So basically there is no properly functioning client for me at the moment. I only have 4 GB of RAM on the laptop so I didn't expect super snappy performance with the full client, but this is just ridiculous. It has to be some bug in the client right? Or is my computer somehow messed up?
« Last Edit: January 24, 2015, 03:37:47 AM by arhag »

Offline mitao

  • Full Member
  • ***
  • Posts: 113
    • View Profile
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #1 on: January 24, 2015, 05:10:23 AM »
Same here. Good job for the 20 100% dev delegates. You deserve the delegates and your end of year bonus. The client become more and more laggy. You almost push me to the limit to quit.


Sent from my iPad using Tapatalk

Offline Brekyrself

  • Sr. Member
  • ****
  • Posts: 360
    • View Profile
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #2 on: January 24, 2015, 06:28:54 AM »
Have you tried the basics?

-Remove BitShares folder and re install latest client.  For Windows its under User/AppData/Roaming/Bitshares.  Of course backup your wallet before doing this!
-Have you tried a fresh install of Linux or Windows?  Anything running in the background? 

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #3 on: January 24, 2015, 09:29:13 AM »
Did you reindex or resync blockchain ?

Offline matt608

  • Hero Member
  • *****
  • Posts: 878
    • View Profile
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #4 on: January 24, 2015, 09:33:59 AM »
I've had the same problems since October.  It takes hours to send a single transaction and I have to use the console.  I don't know why its not fixed first, before adding more features.

Offline bitder

  • Full Member
  • ***
  • Posts: 65
    • View Profile
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #5 on: January 24, 2015, 11:17:48 AM »
I'm running a delegate node and the 0.5.3 upgrade seems to have networking issues.
Looks like it's connecting to itself as a peer and there are race conditions in the code that gets confused about the state of the  sync blocks and disconnects (from itself).
Code: [Select]
Peer <my-own-public-ip>:47595 disconnected us: You offered me a list of more sync blocks than could possibly exist
Peer <my-own-public-ip>:36004 disconnected us: You offered me a list of more sync blocks than could possibly exist
--- there are now 30 active connections to the p2p network
--- there are now 26 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 19 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 17 active connections to the p2p network

Also, on initial start up of 0.5.3 I'm seeing the connection count climb to over 130.
(And I'm about to be bumped off of the top 101...)
wallet_account_set_approval delegate.bitder 1

Offline abit

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #6 on: January 24, 2015, 12:46:12 PM »
I'm running a delegate node and the 0.5.3 upgrade seems to have networking issues.
Looks like it's connecting to itself as a peer and there are race conditions in the code that gets confused about the state of the  sync blocks and disconnects (from itself).
Code: [Select]
Peer <my-own-public-ip>:47595 disconnected us: You offered me a list of more sync blocks than could possibly exist
Peer <my-own-public-ip>:36004 disconnected us: You offered me a list of more sync blocks than could possibly exist
--- there are now 30 active connections to the p2p network
--- there are now 26 active connections to the p2p network
--- there are now 23 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 19 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 17 active connections to the p2p network

Also, on initial start up of 0.5.3 I'm seeing the connection count climb to over 130.
(And I'm about to be bumped off of the top 101...)
Try to remove the peers.leveldb folder and restart?
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline liondani

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #7 on: January 24, 2015, 12:49:09 PM »
My gui client(linux)  has a hard time to keep more than 3 network connections also...
  https://bitshares.OPENLEDGER.info/?r=GREECE  | You are in Control | BUY | SELL | SHORT | SWAP | LOAN | TRADE |  

Offline Riverhead

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #8 on: January 24, 2015, 01:20:47 PM »
It took me literally days to get the client usable on an old 2007 Apple Macbook Pro PC running OSX 10.9.5. Eventually it does calm down if you leave the client open (doesn't have to be unlocked) and just let it trundle through. As can be seen in the tutorial video the client is working fine.


I suspect people are correct when they suggest the client is HD bound for lower ram machines. This machine only has 3GB of RAM but it does eventually get itself sorted.

Offline xiahui135

  • Sr. Member
  • ****
  • Posts: 496
    • View Profile
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #9 on: January 24, 2015, 04:26:12 PM »
0.5.1 is finally usable for me.
Hope the web-wallet will be out asap

Offline vikram

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #10 on: January 24, 2015, 09:51:49 PM »
The CLI client of both versions still has the unbearable typing lag I mentioned last time. Running it with --server and using the web wallet doesn't help. It is very slow. The RPC POST requests have an average latency of around 2 minutes and some of them timeout with an error!

Do you still have the lag in CLI when no wallet is open? Is it equally laggy during syncing and after synced?

Offline arhag

  • Hero Member
  • *****
  • Posts: 1213
    • View Profile
    • My posts on Steem
  • BTS: arhag
  • GitHub: arhag
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #11 on: January 24, 2015, 09:57:38 PM »
The CLI client of both versions still has the unbearable typing lag I mentioned last time. Running it with --server and using the web wallet doesn't help. It is very slow. The RPC POST requests have an average latency of around 2 minutes and some of them timeout with an error!

Do you still have the lag in CLI when no wallet is open? Is it equally laggy during syncing and after synced?

I still have lag whether the wallet is open or not. The blockchain syncing and indexing (not scanning) is what is causing the performance problems and lags. I believe it is a little better after reaching the present block and maintaining sync compared to catching up with the sync, but it may just be my imagination. The point is that the unbearable lag is still present even when the blockchain is never more than 0-20 seconds behind the present block (meaning "after sync").
« Last Edit: January 24, 2015, 09:59:19 PM by arhag »

Offline vikram

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #12 on: January 24, 2015, 10:14:11 PM »
The CLI client of both versions still has the unbearable typing lag I mentioned last time. Running it with --server and using the web wallet doesn't help. It is very slow. The RPC POST requests have an average latency of around 2 minutes and some of them timeout with an error!

Do you still have the lag in CLI when no wallet is open? Is it equally laggy during syncing and after synced?

I still have lag whether the wallet is open or not. The blockchain syncing and indexing (not scanning) is what is causing the performance problems and lags. I believe it is a little better after reaching the present block and maintaining sync compared to catching up with the sync, but it may just be my imagination. The point is that the unbearable lag is still present even when the blockchain is never more than 0-20 seconds behind the present block (meaning "after sync").

Do we know for sure if it's due to HDD seeking (https://bitsharestalk.org/index.php?topic=12887.msg177979#msg177979 )? Or could it possibly be for example the networking threads stealing all CPU? Is there any way you might be able to profile the process to get more info (for example Mac has an easy profile button in task manager)?

Offline arhag

  • Hero Member
  • *****
  • Posts: 1213
    • View Profile
    • My posts on Steem
  • BTS: arhag
  • GitHub: arhag
Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #13 on: January 24, 2015, 10:30:28 PM »
Do we know for sure if it's due to HDD seeking (https://bitsharestalk.org/index.php?topic=12887.msg177979#msg177979 )? Or could it possibly be for example the networking threads stealing all CPU? Is there any way you might be able to profile the process to get more info (for example Mac has an easy profile button in task manager)?

Umm, not sure, I'll see what I can do.

But I should add. I just compiled and ran DevShares 0.6.1. The CLI client had very slight lag during the blockchain sync. Then once the sync was complete it is running very smoothly. The HDD light indicator is not constantly running while running the DVS client unlike the BTS client (and this is also reflected by the lower IORR and IOWR values in htop for the devshares_client threads). My guess is this has to do with the fact that the DVS blockchain is currently very small and new and so the OS just can keep it all in the cache in the RAM rather than going crazy with the HDD seeks.

Offline vikram

Re: 0.5.1 and 0.5.3 are unusable for me
« Reply #14 on: January 24, 2015, 11:33:02 PM »
My guess is this has to do with the fact that the DVS blockchain is currently very small and new and so the OS just can keep it all in the cache in the RAM rather than going crazy with the HDD seeks.

This is likely a large contributing factor. I have also made some additional optimizations to both syncing and wallet scanning in 0.6.x, which will hopefully help you in BTS. Given the problems in this thread I will continue looking for more low-hanging fruit in terms of removing excessive disk accesses, etc.

Actually, since you have been testing different builds, maybe you also want to try a CLI build of commit 1100744c23571392d14d270d6a69541f0174aa05 (current HEAD of bitshares branch) and see if there is any performance difference. That has all the latest code merged in as of Friday night, and should still be syncing successfully. It's of course not an official version so do not trust funds to it.
« Last Edit: January 24, 2015, 11:39:55 PM by vikram »

 

Google+