[eMule-Web]

[eMule-Web] (http://www.emule-web.de/board/)
-   Xtreme MOD (http://www.emule-web.de/board/xtreme-mod/)
-   -   failed upload sessions socket (http://www.emule-web.de/board/12710-failed-upload-sessions-socket.html)

moron 4. July 2007 22:06

failed upload sessions socket
 
servus,

ich bin momentan ein bisschen unzufrieden mit meinem upload:

Code:

eMule v0.48a Xtreme 6.0 Statistics [moron]

Transfer
  Session UL:DL Ratio: 1.76 : 1
  Session UL:DL Ratio (Friends UL excluded): 1.76 : 1
  Cumulative UL:DL Ratio: 1 : 2.36
  Uploads
      Session
        Uploaded Data: 102.82 MB / 116.55 MB
        Uploaded Data to Friend Slots (Session): 0 Bytes
        Active Uploads/Needed to fill Bandwidth: 6
        Total Uploads: 7
        Waiting Uploads: 3818
        Upload Sessions: 80
            Total successful upload sessions: 30 (37.50%) (active: 7, socket: 3, completed: 19, cancelled/ended: 1, different file: 0, exception: 0,blocking: 0, others: 0)
            Total failed upload sessions: 50 (62.50%) (socket: 50, completed: 0, cancelled/ended: 0, different file: 0, exception: 0,blocking: 0, others: 0)
            Average Uploaded Per Session: 3.43 MB
            Average upload time: 9:52 Minutes
        Total Overhead (Packets): 3.80 MB (65.31 k)
      Cumulative
  Downloads
      Session
        Downloaded Data: 58.42 MB / 76.56 MB
        Completed Downloads: 0
        Active Downloads (chunks): 5
        Found Sources: 5785
        Download Sessions: 22
            Successful Download Sessions: 21 (95.5%) (active: 5, paused: 0, no needed part: 0, timeout: 7, socket: 7, out of part: 2, exception: 0, others: 0)
            Failed Download Sessions: 1 (4.5%) (paused: 0, no needed part: 0, timeout: 1, socket: 0, out of part: 0, exception: 0, others: 0)
            Average Downloaded Per Session: 2.78 MB
            Average Download Time: 7:13 Minutes
        Gained Due To Compression: 419 KB (0.7%)
        Lost Due To Corruption: 0 Bytes (0.0%)
        Parts Saved Due To I.C.H: 0
        Total Overhead (Packets): 4.05 MB (65.97 k)
      Cumulative
Connection
  Session
      General
        Reconnects: 0
        Active Connections (estimate): 184 (Half:53 | Compl:55 | Other:76)
        Average Connections (estimate): 172
        Peak Connections (estimate): 501
        Max Connection Limit Reached: 9 : 04.07.2007 22:38:31
      Upload
        Upload-Speed: 46.3 KB/s
        Average Uploadrate: 43.7 KB/s
        Max Upload Rate: 47.9 KB/s
        Max Average Upload Rate: 43.7 KB/s
      Download
  Cumulative
Time Statistics
Clients
Servers
Shared Files
Disk Space

habt ihr ne ahnung woher die fehlgeschlagenen sessions kommen könnten?

upload gesundheit eigentlich immer (wenn ich grad mal schaue) bei 100%
wobei der upload graph doch hier und da einbrüche hat.

upload kapazität = 66 KB/s

max = 500
max/5 = 50
halbe = 199

quellen kanpp 6000

NAFC ist an

hatte NAFC bisher immer aus, da war mir das problem bisher nicht aufgefallen...

Verlierer 4. July 2007 23:37

Klarer Fall von verhunzten Einstellungen soweit ich das sehe :naughty
max/5 = runter auf 20
halbe = runter auf 48

Vielleicht die max Verbindungen auch mal auf 400 reduzieren. Sind 66kB auch wirklich höchstens 80% deiner Uploadbandbreite? Falls ja: Mach mal runter auf 70%

moron 5. July 2007 16:00

Zitat:

Zitat von Verlierer (Beitrag 126348)
Klarer Fall von verhunzten Einstellungen soweit ich das sehe :naughty
max/5 = runter auf 20
halbe = runter auf 48

Vielleicht die max Verbindungen auch mal auf 400 reduzieren. Sind 66kB auch wirklich höchstens 80% deiner Uploadbandbreite? Falls ja: Mach mal runter auf 70%

wieso verhunzte einstellungen?

der rechner hängt direkt am netz. kein router dazwischen. so wie ich das sehe gibt es keinen grund sparsam zu sein beim verbindungsaufbau.

66kb sind nicht 80% sondern 100%
das UL-limit ist eingestellt auf 50kb/s

Verlierer 5. July 2007 18:12

Zitat:

Zitat von moron (Beitrag 126390)
so wie ich das sehe gibt es keinen grund sparsam zu sein beim verbindungsaufbau.

Falsch. Auch ohne Router kannst du mit utopischen Werten eine Überlastung von Muli/Windows/Modem herbeiführen.

Hauptaugenmerk liegt mir auf halben Verbindungen, die sollten auf jeden Fall runter und Windows dann am besten auch zurück patchen. Wie sieht denn mit der Downloadanzahl und der, der gefundenen Quellen aus? Könnte das Mulchen schlichtweg überladen sein?

moron 9. July 2007 12:25

verlierer,

du hattest recht!

ich weiss zwar nicht wo der flaschenhals ist, aber die einstellungen waren zu aggressiv. ich hab die verbindungen mal auf "failsave" runtergedreht:

max. verbindungen: 300
max / 5 seconds: 25
halboffene: 50

ohne NAFC
Code:

eMule v0.48a Xtreme 6.0 Statistics [moron]

Transfer
  Session UL:DL Ratio: 1 : 1.73
  Session UL:DL Ratio (Friends UL excluded): 1 : 1.73
  Cumulative UL:DL Ratio: 1 : 2.10
  Uploads
      Session
        Uploaded Data: 1.74 GB / 2.01 GB
        Uploaded Data to Friend Slots (Session): 0 Bytes
        Active Uploads/Needed to fill Bandwidth: 5
        Total Uploads: 7
        Waiting Uploads: 7375
        Upload Sessions: 457
            Total successful upload sessions: 437 (95.62%) (active: 7, socket: 70, completed: 328, cancelled/ended: 17, different file: 0, exception: 0,blocking: 15, others: 0)
            Total failed upload sessions: 20 (4.38%) (socket: 14, completed: 0, cancelled/ended: 5, different file: 0, exception: 0,blocking: 0, others: 1)
            Average Uploaded Per Session: 4.08 MB
            Average upload time: 10:44 Minutes
        Total Overhead (Packets): 48.63 MB (903.40 k)
      Cumulative
  Downloads
      Session
        Downloaded Data: 3.02 GB / 3.94 GB
        Completed Downloads: 5
        Active Downloads (chunks): 19
        Found Sources: 6945
        Download Sessions: 823
            Successful Download Sessions: 625 (75.9%) (active: 19, paused: 3, no needed part: 50, timeout: 127, socket: 121, out of part: 305, exception: 0, others: 0)
            Failed Download Sessions: 198 (24.1%) (paused: 0, no needed part: 8, timeout: 22, socket: 162, out of part: 6, exception: 0, others: 0)
            Average Downloaded Per Session: 4.95 MB
            Average Download Time: 20:06 Minutes
        Gained Due To Compression: 46.56 MB (1.5%)
        Lost Due To Corruption: 1.63 MB (0.1%)
        Parts Saved Due To I.C.H: 5
        Total Overhead (Packets): 46.85 MB (1.01 M)
      Cumulative
Connection
  Session
      General
        Reconnects: 0
        Active Connections (estimate): 174 (Half:5 | Compl:52 | Other:117)
        Average Connections (estimate): 180
        Peak Connections (estimate): 292
        Max Connection Limit Reached: 0
      Upload
        Upload-Speed: 44.3 KB/s
        Average Uploadrate: 44.0 KB/s
        Max Upload Rate: 48.1 KB/s
        Max Average Upload Rate: 44.5 KB/s
      Download
  Cumulative
Time Statistics
  Statistics last reset: 01.07.2007 12:22:09
  Time Since Last Reset: 6 Days 10:52 Hours
  Session
      Runtime: 11:32 Hours
      Transfer Time: 11:29 Hours (99.6%)
      Current Server Duration: 0 Seconds (0.0%)
      Total Server Duration: 2:16 Hours (19.7%)
  Cumulative
  Projected Averages
Clients
Servers
Shared Files
Disk Space

mit NAFC
Code:

eMule v0.48a Xtreme 6.0 Statistics [moron]

Transfer
  Session UL:DL Ratio: 1 : 1.53
  Session UL:DL Ratio (Friends UL excluded): 1 : 1.53
  Cumulative UL:DL Ratio: 1 : 2.03
  Uploads
      Session
        Uploaded Data: 1.69 GB / 1.93 GB
        Uploaded Data to Friend Slots (Session): 0 Bytes
        Active Uploads/Needed to fill Bandwidth: 5
        Total Uploads: 7
        Waiting Uploads: 7355
        Upload Sessions: 502
            Total successful upload sessions: 481 (95.82%) (active: 7, socket: 80, completed: 357, cancelled/ended: 18, different file: 0, exception: 0,blocking: 19, others: 0)
            Total failed upload sessions: 21 (4.18%) (socket: 12, completed: 0, cancelled/ended: 7, different file: 0, exception: 1,blocking: 0, others: 1)
            Average Uploaded Per Session: 3.60 MB
            Average upload time: 9:12 Minutes
        Total Overhead (Packets): 44.06 MB (845.14 k)
      Cumulative
  Downloads
      Session
        Downloaded Data: 2.60 GB / 3.34 GB
        Completed Downloads: 0
        Active Downloads (chunks): 26
        Found Sources: 7123
        Download Sessions: 757
            Successful Download Sessions: 558 (73.7%) (active: 26, paused: 0, no needed part: 12, timeout: 112, socket: 123, out of part: 285, exception: 0, others: 0)
            Failed Download Sessions: 199 (26.3%) (paused: 0, no needed part: 3, timeout: 20, socket: 169, out of part: 7, exception: 0, others: 0)
            Average Downloaded Per Session: 4.77 MB
            Average Download Time: 19:11 Minutes
        Gained Due To Compression: 36.69 MB (1.4%)
        Lost Due To Corruption: 0 Bytes (0.0%)
        Parts Saved Due To I.C.H: 0
        Total Overhead (Packets): 42.04 MB (920.47 k)
      Cumulative
Connection
  Session
      General
        Reconnects: 0
        Active Connections (estimate): 188 (Half:5 | Compl:48 | Other:135)
        Average Connections (estimate): 186
        Peak Connections (estimate): 276
        Max Connection Limit Reached: 0
      Upload
        Upload-Speed: 41.5 KB/s
        Average Uploadrate: 43.7 KB/s
        Max Upload Rate: 49.3 KB/s
        Max Average Upload Rate: 44.5 KB/s
      Download
  Cumulative
Time Statistics
  Statistics last reset: 01.07.2007 12:22:09
  Time Since Last Reset: 7 Days 9:29 Hours
  Session
      Runtime: 11:16 Hours
      Transfer Time: 11:15 Hours (99.9%)
      Current Server Duration: 0 Seconds (0.0%)
      Total Server Duration: 0 Seconds (0.0%)
  Cumulative
  Projected Averages
Clients
Servers
Shared Files
Disk Space

alles in allem denke ich dick im grünen bereich...

allerdings würde ich trotzdem interessieren, was das "socket" bei den verbindungen in der statistik bedeutet...

Verlierer 9. July 2007 20:34

Zitat:

Zitat von moron (Beitrag 126529)
verlierer,

du hattest recht!

Glaubst gar nicht wie oft ich das zu hören bekomme :-)

Zitat:

Zitat von moron (Beitrag 126529)
allerdings würde ich trotzdem interessieren, was das "socket" bei den verbindungen in der statistik bedeutet...

Bei einem Socket Error war die Verbindung zwischen dir einen Client so beschizzen, dass sie abgebrochen wurde.


Alle Zeitangaben in WEZ +1. Es ist jetzt 01:39 Uhr.

Powered by vBulletin® Version 3.8.3 (Deutsch)
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2011, Crawlability, Inc.


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102