Vivek Gupta wrote: > We have upgrade the Slony from 1.1.5 to 2.0.4rc2 and additionally the > platform has been migrated from 32-bit to 64-bit. To our strange ‘slon’ > process is taking ~250 MB of memory although its usage was in KBs > earlier. What could be the root cause either slony upgrade or the > platform change?
How many nodes are in your cluster and how many paths between the nodes are defined? One large factor in how much memory slon will use is the number of connections that slon has to make to remote databases. For each path between the node the slon is assinged to it will need 2 threads per path + a libpq connection. Another factor that might be influencing what you see it that I think in 1.1.5 you would have had to manually add listeners to your cluster while in 2.0 (and 1.2 I think) you get listeners for each path. On 32 bit linux I'm seeing a slon with paths to 2 other nodes using just under 70megs of virtual size while the same test with 64bit linux is using about 144megs. (This is with 2.0.4 but 1.2.21 seems to have memory usage in the same range) Memory usage (particularly with many paths) seems higher than I would like it to be. Why we use so much memory should be investigated. > > > > With regards, > > Vivek Gupta > > > ------------------------------------------------------------------------ > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://lists.slony.info/mailman/listinfo/slony1-general -- Steve Singer Afilias Canada Data Services Developer 416-673-1142 _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
