ProtaX Performance (RAM usage) - Page 2
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

ProtaX Performance (RAM usage)

Started by BoJlk, 07 November, 2004, 00:57:18

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

BoJlk

Well i've noticed that when i enable CMD's
in Users and Chats the Memory Usage starts to Climb up...when i had 97MB i've disabled it and it droped to around 80MB...

bastya_elvtars

QuoteOriginally posted by BoJlk
Well i've noticed that when i enable CMD's
in Users and Chats the Memory Usage starts to Climb up...when i had 97MB i've disabled it and it droped to around 80MB...

think of the fact that the computer has to show the cmds continually

[10:47]  (81.185.90.183) > $Key A@G?/%DCN096%/?wgG"!T?????ĂPň?07??52?31rđŕ??/%DCN000%/łň2|
[10:47]  (81.185.90.183) > $ValidateNick biigix|
[10:47] biigix (81.185.90.183) > $Version 1,0091|
[10:47] biigix (81.185.90.183) > $GetNickList|
[10:47] biigix (81.185.90.183) > $MyINFO $ALL biigix mldc client$ $DSL$$  11534336$|
[10:47]  (212.90.82.81) > $Key Q?ˇ2?Ő0đă?F!˛/%DCN005%/WBFđ?ŁŐ?SRŇb?Q3Băˇ?A@s˛|
[10:47]  (212.90.82.81) > $ValidateNick mzpppi|
[10:47] x User removed: biigix (Socket 308)
[10:47] hugo_fra_tv2? (81.225.83.109) > $UserIP biigix|
[10:47] mzpppi (212.90.82.81) > $Version 1,0091|
[10:47] mzpppi (212.90.82.81) > $GetNickList|
[10:47] mzpppi (212.90.82.81) > $MyINFO $ALL mzpppi mldc client$ $DSL$$  11534336$|
[10:47] mzpppi (212.90.82.81) > $RevConnectToMe [FIN]Killian mzpppi|
[10:47] mzpppi (212.90.82.81) > $ConnectToMe [FIN]Killian 212.90.82.81:4444|
[10:47] mzpppi (212.90.82.81) > $RevConnectToMe [FIN]Killian mzpppi|
[10:47] mzpppi (212.90.82.81) > $ConnectToMe [FIN]Killian 212.90.82.81:4444|
[10:47] x User removed: mzpppi (Socket 380)
[10:47] hugo_fra_tv2? (81.225.83.109) > $UserIP mzpppi|
[10:47]  (81.153.39.84) > $Key вƒ?Qq 3ă˛??!?&/%DCN000%/?đ??ˇC?Ă0?/%DCN036%/ćR?CĐ!"?!BPR?|
[10:47]  (81.153.39.84) > $ValidateNick wnyixn|
[10:47] wnyixn (81.153.39.84) > $Version 1,0091|
[10:47] wnyixn (81.153.39.84) > $GetNickList|
[10:47] wnyixn (81.153.39.84) > $MyINFO $ALL wnyixn mldc client$ $DSL$$  11534336$|
[10:47] x User removed: wnyixn (Socket 308)
[10:47] hugo_fra_tv2? (81.225.83.109) > $UserIP wnyixn|
[10:47]  (82.135.28.44) > $Key ?pd?ł#0!?đaq?/%DCN000%/@Ą?Cc?p!v/%DCN005%/Ńe@"W/%DCN096%/?&?đ?WĐ????|
[10:47]  (82.135.28.44) > $ValidateNick abewad|
[10:47] abewad (82.135.28.44) > $Version 1,0091|
[10:47] abewad (82.135.28.44) > $GetNickList|
[10:47] abewad (82.135.28.44) > $MyINFO $ALL abewad mldc client$ $DSL$$  11534336$|
[10:47] x User removed: abewad (Socket 308)
[10:47] hugo_fra_tv2? (81.225.83.109) > $UserIP abewad|
[10:47] [HUN]hungaricum (147.229.192.34) > $Search Hub:[HUN]hungaricum F?T?0?1?primus|
[10:47] [HUN]hungaricum (147.229.192.34) > $RevConnectToMe [HUN]hungaricum Nidaros|
[10:47] Nidaros (80.202.30.254) > $ConnectToMe [HUN]hungaricum 80.202.30.254:4012|
[10:47]  (69.111.154.210) > $Key ?U"S GWBR??Rňˇňq?/%DCN036%/1CC%?pB/%DCN096%/@@ ?P??7?V!12ƒ|
[10:47]  (69.111.154.210) > $ValidateNick jckqkt|
[10:47] jckqkt (69.111.154.210) > $Version 1,0091|
[10:47] jckqkt (69.111.154.210) > $GetNickList|
[10:47] jckqkt (69.111.154.210) > $MyINFO $ALL jckqkt mldc client$ $DSL$$  11534336$|
[10:47] x User removed: jckqkt (Socket 328)
[10:47] hugo_fra_tv2? (81.225.83.109) > $UserIP jckqkt|
[10:47]  (67.71.84.9) > $Key v?˛0b? ŕ?uŃ?ŕ'ć?ŕ 1Ŕr R??ŕ&F??ł#g/%DCN000%/uCń?|
[10:47]  (67.71.84.9) > $ValidateNick xDonkey_User|
[10:47] xDonkey_User (67.71.84.9) > $Version 1,0091|
[10:47] xDonkey_User (67.71.84.9) > $GetNickList|
[10:47] xDonkey_User (67.71.84.9) > $MyINFO $ALL xDonkey_User mldc client$ $DSL$$  11534336$|
[10:47] x User removed: xDonkey_User (Socket 328)

This has to be stored in ram,  so yes, it stores a lot. Disable that window. (forgot this)
Everything could have been anything else and it would have just as much meaning.

BoJlk

well, does it have a *.log file somewhere?

bastya_elvtars

QuoteOriginally posted by BoJlk
well, does it have a *.log file somewhere?

ptokax is able to log the mainchat only. These commands are not required to log, cause they are plain dc protocol commands. You have notning to do them, the whole function is only good for developing purposes.
Everything could have been anything else and it would have just as much meaning.

BoJlk

Okey...good enought for me.

Saivert

DCH++ is a hubsoft with small memory footprint, and you can extend it with plugins and LUA scripts.
It's evolving to an ADC protocol hubsoft as we speak.
ADC promises better efficiency as the command names are shorter (RCM instead of $RevConnectMe) and all the other things that come with ADC (better search, increased security, CID, etc..).

http://dchpp.digitalbrains.com/

PPK

QuoteOriginally posted by Saivert
ADC promises better efficiency as the command names are shorter (RCM instead of $RevConnectMe)
xRCM mycid targetcid proto TO\n send in UTF-8 (something like 2 bytes per char) instead of $RevConnectToMe mynick targetnick| ... good choice of example how ADC use more badwith :D
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Saivert

I know all this, that isn't the real question here. This thread was about the efficiency of the hub software itself, not what data flows through the net (I hate protocol wars). We all know that ADC will takeover anytime soon and that It might require more bandwith. But I don't think that matters becuase the ADC protocol promises so many benefits that it out-weighs the larger connection strings. And who knows, maybe becuase of the larger connections string it requires fewer transactions in order to a simple task as most of the information is sendt in one go, and silly protocol extentions are now a thing of the past.

The internet itself is based on very old technology and would require a overhaul itself (HTTP is connection-less, lacks native session support which forces scripts to use hacks in order to make it happen).

SMF spam blocked by CleanTalk