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: Cannot sync new client if less 2G Ram  (Read 401 times)

0 Members and 1 Guest are viewing this topic.

Offline joele

  • Sr. Member
  • ****
  • Posts: 459
    • View Profile
Cannot sync new client if less 2G Ram
« on: October 29, 2014, 06:22:50 AM »

I have 32bit win7 with 8G ram but only 3G available due to 32bit win7 system allocation

I backed up my /BitSharesX dir (database) so I can restore and repeat the syncing.

Installed 0.4.23 and start syncing, while at 82% complete it eats up 98% of my available memory then crash.

So I tried memory optimizer software still crash, also tried different approach still it crashes due to low memory.

The only way to sync it is in the client mode that will take hours even days to complete.
or just upgrade your memory.

FYI

edit: I managed to optimized the RAM and still it keep crashing at 82%, so I guess it's not the RAM, something with the 32bit for this version.
« Last Edit: October 29, 2014, 02:23:09 PM by joele »

Offline abit

Re: Cannot sync new client if less 2G Ram
« Reply #1 on: October 29, 2014, 03:42:18 PM »
I'm running the client in Ubuntu 14.04 LTS. (maybe debug mode?)
Every time re-indexing the block chain database, it eats more RAM, say about 3GB for 0.4.20, more than 3GB for 0.4.23.
So.. if you run the client with less than 3G RAM, it's better to start from an empty database, don't upgrade from a old chain database.

Another experience in a old version of client: when syncing from a chain server, the client eats more and more RAM as well. Restart works. Maybe there is a memory leak bug.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline emf

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
Re: Cannot sync new client if less 2G Ram
« Reply #2 on: October 29, 2014, 09:05:37 PM »
The next build will allow 32-bit windows clients access to another gigabyte of RAM, which is enough to allow it to sync or re-index the blockchain (at least for another week or two).

The only way I can think to do it with the current win32 build is to sync from the network in several stages.  Launch the client and watch the memory in Task Manager.  When you see it getting near 2GB, shutdown and launch again.  After two or three tries, you should be up to date.


zerosum

  • Guest
Re: Cannot sync new client if less 2G Ram
« Reply #3 on: October 29, 2014, 09:14:00 PM »
The next build will allow 32-bit windows clients access to another gigabyte of RAM, which is enough to allow it to sync or re-index the blockchain (at least for another week or two).

The only way I can think to do it with the current win32 build is to sync from the network in several stages.  Launch the client and watch the memory in Task Manager.  When you see it getting near 2GB, shutdown and launch again.  After two or three tries, you should be up to date.

I was thinking of doing this and was also advised that this might work. Did you try it already?

Offline emf

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
Re: Cannot sync new client if less 2G Ram
« Reply #4 on: October 30, 2014, 02:21:05 PM »
It works; I've done syncing in multiple stages before when I was trying to figure out if the fact that later blocks sync slower than earlier blocks is because of this excessive memory usage.  (spoiler: it's not, later blocks are just as slow when the client's memory usage is 500MB as they are when it's 2GB.)

The new 0.4.23.1 build lets you sync from scratch without stopping.

Offline abit

Re: Cannot sync new client if less 2G Ram
« Reply #5 on: November 03, 2014, 05:09:57 PM »
It works; I've done syncing in multiple stages before when I was trying to figure out if the fact that later blocks sync slower than earlier blocks is because of this excessive memory usage.  (spoiler: it's not, later blocks are just as slow when the client's memory usage is 500MB as they are when it's 2GB.)

The new 0.4.23.1 build lets you sync from scratch without stopping.
Sure it works for syncing, I always sync this way in my winxp box.
But I don't think it will work for re-indexing..
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline vikram

Re: Cannot sync new client if less 2G Ram
« Reply #6 on: November 04, 2014, 08:54:10 PM »
A significant memory leak has been found and fixed for upcoming v0.4.24: https://github.com/BitShares/bitshares/issues/759

zerosum

  • Guest
Re: Cannot sync new client if less 2G Ram
« Reply #7 on: November 04, 2014, 09:28:02 PM »
A significant memory leak has been found and fixed for upcoming v0.4.24: https://github.com/BitShares/bitshares/issues/759

Seem likely to be the same issue, but if not

when the client is running (regular use, not re-indexing) for long time (hours) the memory consumed grows steadily. I have seen it reaching 700 MB but often it go to 500+ MB.

« Last Edit: November 05, 2014, 05:24:21 AM by tonyk2 »

 

Google+