Page 4 of 5 FirstFirst 12345 LastLast
Results 61 to 80 of 96
  1. #61
    Community Member J1NG's Avatar
    Join Date
    Jun 2009
    Posts
    1,791

    Default

    Quote Originally Posted by sebastianosmith View Post
    Just an FYI, there was a discussion over on the LOTRO forums about this exact issue about 10 months ago. They did get a little sidetracked over bits and bytes but came to similar conclusions.
    Wish you'd posted that before I started testing on this. Still waiting on the character selection screen to load on a 0.50 setting is painstakingly slow. In excess of 60 minutes now, and still not there.

    Will just put a high number in the setting and leave it be once I finally get through.

    J1NG
    Thelanis: Yijing (*Completionist* TR 19 36 Point Warforged Monk Level 20 / Epic Level 10)
    Thelanis: Pocket-Monks: Sightblur, Peashoote, Jigglypath.
    Invisible Fences, unkillable Target Practice Dummy's, Shared Bank's, Pale Lavender Ioun Stones, the dimensional barrier between Eberron and Shavarath, I've broken them all...

  2. #62
    Community Member mobrien316's Avatar
    Join Date
    Dec 2009
    Location
    New England, USA
    Posts
    2,271

    Default

    I reset mine from 0.0 to 3000. The game loaded instantly, or near enough as to make no difference.

    Prior to this, every time I started the game I could get to character selection fairly quickly, and then selecting a character would usually (nearly always) cause a long, long load time and end up with a load with a red X, followed by a lost connection. After that happened once I would be able to log in normally.
    All on Thelanis: Archenpaul Sixblade, Archernicus Thornwood, Gregorovic Redcloak, Jaklomeo Evermug, Jarladdin Nalfesne, Jonathraxius Kane, and Praetoreus Silvershield.

    Sole member of Guinness Knights (Level 105)

    Cogito ergo summopere periculosus.

  3. #63
    Community Member Hawkwier's Avatar
    Join Date
    Jul 2010
    Location
    Scotland
    Posts
    319

    Question No Difference

    Not very scientific, but I tried this today on 3 different edits...

    0.0
    9999.0
    5000.0

    Results showed no significant difference at all.

    Only difference noted was after first login, but that happens every time and is dwn to the Windows cache as noted earlier.

  4. #64
    Founder & Hero
    2016 DDO Players Council
    Uska's Avatar
    Join Date
    Jan 2006
    Location
    Behind you with a claw hammer
    Posts
    25,337

    Default

    Will give it a try and hope


    Beware the Sleepeater

  5. #65
    Community Member Singular's Avatar
    Join Date
    Mar 2010
    Posts
    2,996

    Default Changed my setting to 5000

    I noticed no speed increases in any aspect of the game. It didn't load faster, my characters don't zone faster. No idea why not.

  6. #66
    Community Member Flavilandile's Avatar
    Join Date
    Aug 2010
    Location
    France
    Posts
    3,908

    Default

    Quote Originally Posted by Singular View Post
    I noticed no speed increases in any aspect of the game. It didn't load faster, my characters don't zone faster. No idea why not.
    You're on a SSD Drive ?

    I didn't notice anything either...
    Except maybe a faster ability to move after loading when I change alts. I'll have to make more checks tonight.
    On G-Land : Flavilandile, Blacklock, Yaelle, Millishande, Larilandile, Gildalinde, Tenalafel, and many other...

  7. #67
    Community Member J1NG's Avatar
    Join Date
    Jun 2009
    Posts
    1,791

    Default

    The following was a quick and dirty test for loading DDO, but not other areas where it may be more important such as in Mabar.

    Account has 12 toon slots. All used up. Account upgrades = everything. Full Premium Account. Non VIP.

    Toon is a Bladeforged
    Situated on a Windspyre Falcon
    Buffs: Auctioneer, Banker, Bar

    Machine 1:
    i5 3570 (Don't ask why not the K, just don't...)
    16 GB 1600Mhz RAM
    SATAI HD (attached to SATAII)
    Windows 8.1

    At 16.0 setting
    Cold boot:
    49s to reach selection screen
    191s to movement in game after selecting toon
    130s to visible buffs from ship in game

    Restart of client:
    32s to reach selection screen
    60s to movement in game after selecting soon
    60s to visible buffs from ship in game

    At 32.0 setting
    Cold boot:
    33s to reach selection screen
    192s to movement in game after selecting toon
    192s to visible buffs from ship in game

    Restart of client:
    16s to reach selection screen
    30s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 64.0 setting
    Cold boot:
    27s to reach selection screen
    196s to movement in game after selecting toon
    196s to visibile buffs from ship in game

    Restart of client:
    10s to reach selection screen
    24s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 128.0 setting
    Cold boot:
    25s to reach selection screen
    204s to movement in game after selecting toon
    204s to visible buffs from ship in game

    Restart of client:
    10s to reach selection screen
    17s to movement in game after selecting toon
    17s to visible buffs from ship in game

    At 256.0 setting
    Cold boot:
    25s to reach selection screen
    206s to movement in game after selecting toon
    206s to visible buffs from ship in game

    Restart of client:
    9s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game.

    ---

    Now here's a same test from a different machine with faster hardware:

    Machine 2:
    i7 3820
    64 GB 1333Mhz RAM
    32 GB Ramdisk
    Windows 8.1

    At 16.0 setting
    Cold boot:
    34s to reach selection screen
    71s to movement in game after selecting toon
    71s to visible buffs from ship in game

    Restart of client:
    35s to reach selection screen
    69s to movement in game after selecting soon
    18s to visible buffs from ship in game

    At 32.0 setting
    Cold boot:
    19s to reach selection screen
    53s to movement in game after selecting toon
    42s to visible buffs from ship in game

    Restart of client:
    19s to reach selection screen
    34s to movement in game after selecting toon
    11s to visible buffs from ship in game

    At 64.0 setting
    Cold boot:
    11s to reach selection screen
    25s to movement in game after selecting toon
    23s to visibile buffs from ship in game

    Restart of client:
    11s to reach selection screen
    24s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 128.0 setting
    Cold boot:
    10s to reach selection screen
    18s to movement in game after selecting toon
    7s to visible buffs from ship in game

    Restart of client:
    10s to reach selection screen
    18s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 256.0 setting
    Cold boot:
    10s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game

    Restart of client:
    9s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game.

    ---

    There's a few interesting pieces you can gether from this data.

    1. As others have said, Windows cache is your speed up plan on a client restart.
    2. Speeds between 16.0 and 64.0 show performance increases for DDO load times, even on a cold boot. Which means if you've been limiting or have had your connection limited somehow, then there's a good chance you will see a slowdown for the initial entry into DDO.
    3. Beyond the initial boot into DDO, Windows Cache essential allows a Hard Drive (76MB/s transfer with ms seek time) to be comparable to a Ramdisk (6000MB/s transfer with ns seek time). In short, don't scrimp on RAM.
    4. The sweet spot for loading appears to be between 64.0 and 128.0. This appears to be the fastest you can load the game without some seriously overclocked high end hardware.

    So I would again say as I have previously that there are some gains to be made if you're running off older hardware, especially slower storage. But there is only so much to be gained.

    As for big bandwidth situations like Mabar. Well, I can't test that as there's no consistent way to test it properly, so the results will be skewed.

    My recommendation would be to set the setting to 512, 1024 or 2048. Any more and it's unlikely to be useful. But as a multiplier of 4, 8 and 16 (of 128, which appears to be the sweet spot for the connection number) that should in theory cover enough for the most demanding situation from DDO. From eE Red Alert runs to eE Red Alert raids. Although again, this is just speculation at this point, as Mabar has no consistent way to test lag.

    The only other test I was able to perform was the Twelve test (the part when running across the bridge). On the HD, it would consistently freeze a second or less whislt crossing. Using the Ramdisk, not a hitch.

    For most cases, you can assume your typical SSD equates to the Ramdisk in this situation.

    Personally setting the connection to 2048 on all DDO machines...

    J1NG
    Thelanis: Yijing (*Completionist* TR 19 36 Point Warforged Monk Level 20 / Epic Level 10)
    Thelanis: Pocket-Monks: Sightblur, Peashoote, Jigglypath.
    Invisible Fences, unkillable Target Practice Dummy's, Shared Bank's, Pale Lavender Ioun Stones, the dimensional barrier between Eberron and Shavarath, I've broken them all...

  8. #68
    Community Member Sokól's Avatar
    Join Date
    Apr 2013
    Location
    Iceland
    Posts
    580

    Default

    I tried this out last night and it worked very well, my loading screens are very short now and for once I am not the last 1 in quest lol
    Argonnessen: Hilmir - Purkilius - Jinu - Vignir @ Blood Assassin´s

  9. #69
    Community Member IronClan's Avatar
    Join Date
    Jan 2010
    Posts
    8,308

    Default

    Quote Originally Posted by Cauthey_No_CCInfo View Post
    I'd set to 0.0 to time it for you. But, frankly, I'm not concerned with appeasing your skepticism. And, I'd rather not have to sit through a longer login just to time it for you.
    Alrighty then, not sure why you think I was asking you specifically to test for me, as opposed to anyone who was in a position to, to test for everyone who's a little scientifically minded, or reasonably skeptical, or everyone who's inclined to want more evidence than a glowing testimonial or narrative.

    FWIW nothing I did to that number resulted in improved load times, and lowering the number below about 20.0 seemed to degrade performance (throttled the connection speed). This is not to say my results represent everyone. Someone with a messed up connection or some other problem (like DDO not being able to autodetect their connection speed and going with some strange low number that throttled them) might see an abnormal long load time (for example) cut down to a reasonable normal load time by this. Such as the guy that just posted about always being the last one in quest. Worth a try.
    Last edited by IronClan; 10-30-2013 at 06:46 AM.

  10. #70
    Community Member IronClan's Avatar
    Join Date
    Jan 2010
    Posts
    8,308

    Default

    Quote Originally Posted by J1NG View Post
    The following was a quick and dirty test for loading DDO, but not other areas where it may be more important such as in Mabar.

    Account has 12 toon slots. All used up. Account upgrades = everything. Full Premium Account. Non VIP.

    Toon is a Bladeforged
    Situated on a Windspyre Falcon
    Buffs: Auctioneer, Banker, Bar

    Machine 1:
    i5 3570 (Don't ask why not the K, just don't...)
    16 GB 1600Mhz RAM
    SATAI HD (attached to SATAII)
    Windows 8.1

    At 16.0 setting
    Cold boot:
    49s to reach selection screen
    191s to movement in game after selecting toon
    130s to visible buffs from ship in game

    Restart of client:
    32s to reach selection screen
    60s to movement in game after selecting soon
    60s to visible buffs from ship in game

    At 32.0 setting
    Cold boot:
    33s to reach selection screen
    192s to movement in game after selecting toon
    192s to visible buffs from ship in game

    Restart of client:
    16s to reach selection screen
    30s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 64.0 setting
    Cold boot:
    27s to reach selection screen
    196s to movement in game after selecting toon
    196s to visibile buffs from ship in game

    Restart of client:
    10s to reach selection screen
    24s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 128.0 setting
    Cold boot:
    25s to reach selection screen
    204s to movement in game after selecting toon
    204s to visible buffs from ship in game

    Restart of client:
    10s to reach selection screen
    17s to movement in game after selecting toon
    17s to visible buffs from ship in game

    At 256.0 setting
    Cold boot:
    25s to reach selection screen
    206s to movement in game after selecting toon
    206s to visible buffs from ship in game

    Restart of client:
    9s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game.

    ---

    Now here's a same test from a different machine with faster hardware:

    Machine 2:
    i7 3820
    64 GB 1333Mhz RAM
    32 GB Ramdisk
    Windows 8.1

    At 16.0 setting
    Cold boot:
    34s to reach selection screen
    71s to movement in game after selecting toon
    71s to visible buffs from ship in game

    Restart of client:
    35s to reach selection screen
    69s to movement in game after selecting soon
    18s to visible buffs from ship in game

    At 32.0 setting
    Cold boot:
    19s to reach selection screen
    53s to movement in game after selecting toon
    42s to visible buffs from ship in game

    Restart of client:
    19s to reach selection screen
    34s to movement in game after selecting toon
    11s to visible buffs from ship in game

    At 64.0 setting
    Cold boot:
    11s to reach selection screen
    25s to movement in game after selecting toon
    23s to visibile buffs from ship in game

    Restart of client:
    11s to reach selection screen
    24s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 128.0 setting
    Cold boot:
    10s to reach selection screen
    18s to movement in game after selecting toon
    7s to visible buffs from ship in game

    Restart of client:
    10s to reach selection screen
    18s to movement in game after selecting toon
    7s to visible buffs from ship in game

    At 256.0 setting
    Cold boot:
    10s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game

    Restart of client:
    9s to reach selection screen
    17s to movement in game after selecting toon
    7s to visible buffs from ship in game.

    ---

    There's a few interesting pieces you can gether from this data.

    1. As others have said, Windows cache is your speed up plan on a client restart.
    2. Speeds between 16.0 and 64.0 show performance increases for DDO load times, even on a cold boot. Which means if you've been limiting or have had your connection limited somehow, then there's a good chance you will see a slowdown for the initial entry into DDO.
    3. Beyond the initial boot into DDO, Windows Cache essential allows a Hard Drive (76MB/s transfer with ms seek time) to be comparable to a Ramdisk (6000MB/s transfer with ns seek time). In short, don't scrimp on RAM.
    4. The sweet spot for loading appears to be between 64.0 and 128.0. This appears to be the fastest you can load the game without some seriously overclocked high end hardware.

    So I would again say as I have previously that there are some gains to be made if you're running off older hardware, especially slower storage. But there is only so much to be gained.

    As for big bandwidth situations like Mabar. Well, I can't test that as there's no consistent way to test it properly, so the results will be skewed.

    My recommendation would be to set the setting to 512, 1024 or 2048. Any more and it's unlikely to be useful. But as a multiplier of 4, 8 and 16 (of 128, which appears to be the sweet spot for the connection number) that should in theory cover enough for the most demanding situation from DDO. From eE Red Alert runs to eE Red Alert raids. Although again, this is just speculation at this point, as Mabar has no consistent way to test lag.

    The only other test I was able to perform was the Twelve test (the part when running across the bridge). On the HD, it would consistently freeze a second or less whislt crossing. Using the Ramdisk, not a hitch.

    For most cases, you can assume your typical SSD equates to the Ramdisk in this situation.

    Personally setting the connection to 2048 on all DDO machines...

    J1NG
    J1ng great testing would have really liked to have seen you baseline with a 0.00 autodetect setting. 16.0 is surely throttling, as similar amounts for me throttled down the character data loading screen effectively a standstill lower numbers than 12 were effectively a complete halt of the "receiving character data" load bar (5.0 resulted in the game reporting give or take 0.70 kbps going from memory)

  11. #71
    Community Member J1NG's Avatar
    Join Date
    Jun 2009
    Posts
    1,791

    Default

    Quote Originally Posted by IronClan View Post
    J1ng great testing would have really liked to have seen you baseline with a 0.00 autodetect setting. 16.0 is surely throttling, as similar amounts for me throttled down the character data loading screen effectively a standstill lower numbers than 12 were effectively a complete halt of the "receiving character data" load bar (5.0 resulted in the game reporting give or take 0.70 kbps going from memory)
    The 0.00 can be done in about an hours time when I'm free. Although I'm going to guess that it's going to be the same as 128.0 setting from past observations.

    J1NG
    Thelanis: Yijing (*Completionist* TR 19 36 Point Warforged Monk Level 20 / Epic Level 10)
    Thelanis: Pocket-Monks: Sightblur, Peashoote, Jigglypath.
    Invisible Fences, unkillable Target Practice Dummy's, Shared Bank's, Pale Lavender Ioun Stones, the dimensional barrier between Eberron and Shavarath, I've broken them all...

  12. #72
    Founder & Hero cdbd3rd's Avatar
    Join Date
    Jan 2006
    Location
    Escaping Mizzery in the Tavern Attic.
    Posts
    25,730

    Default

    Given the number of trusted names who have already posted thru thread, I gave this a try.


    I set to 2048. (I use the pre-loader. I'm on an older Win 7 off-the-shelf puter, onboard Nvidia graphics, 7200 HDD.)

    I had not experienced the Mabar lag, but a great frustration for me has been the Craft Hall decon interface. I decon everything I can get my mitts on, until past year or so. Currently, I can decon 1 or 2 items before a horrendous lag envelops the machine and every item following incurs 20-30 seconds of frozen hang time.

    So...

    I loaded into the craft hall. Seemed to be a bit faster, but not earth-shattering. However, I gathered a half-dozen items off AH and fired up the decon monster. All 6 ran smooth without a hang. Grabbed another 8 items, and those ran thru the machine as fast as I could drag/drop/click.

    For what it's worth, that alone has made this setting an awesome tweak. Many thanks to the OP and everyone following who tested it out. (Not enough +rep to go around. Sorry. ...but I did make Mindos' Greenis swell a bit. That's embarassing. lol!)


    EDIT: Went back in and ran thru some loading screens. Remarkable difference in first loads, and repeated entries were near instantaneous. Even going back into the Craft Hall the load bar barely had time to pop up before I was thru & in.
    Last edited by cdbd3rd; 10-30-2013 at 07:06 AM.
    CEO - Cupcake's Muskateers, Thelanis
    DDO Freebies

  13. #73

    Default

    Quote Originally Posted by J1NG View Post
    Wish you'd posted that before I started testing on this. Still waiting on the character selection screen to load on a 0.50 setting is painstakingly slow. In excess of 60 minutes now, and still not there.
    In future I will endeavor to anticipate your desires with more alacrity...

    Quote Originally Posted by J1NG View Post
    The following was a quick and dirty test for loading DDO, but not other areas where it may be more important such as in Mabar.

    <...SNIP DATA...>

    So I would again say as I have previously that there are some gains to be made if you're running off older hardware, especially slower storage. But there is only so much to be gained.

    ...

    My recommendation would be to set the setting to 512, 1024 or 2048. Any more and it's unlikely to be useful. But as a multiplier of 4, 8 and 16 (of 128, which appears to be the sweet spot for the connection number) that should in theory cover enough for the most demanding situation from DDO. From eE Red Alert runs to eE Red Alert raids. Although again, this is just speculation at this point, as Mabar has no consistent way to test lag.

    J1NG
    Firstly, many thanks for taking the time to do this. I hope other members of the community are also appreciative of your efforts.

    I suspect the gains seen in initial loads can be attributed to populating character, inventory and maybe world data from the server a smidge faster, but, as you have yet again demonstrated, memory caching provides the lion's share of the performance gains.

    My only remaining question would be what, considering that some who have reported significant performance increases are not mistaken, is causing the auto-detect routine to supply a value other than that 128 "sweet spot" which I think is the default.

    Once again, thank you for providing some data on this subject.
    The newest computer can merely compound, at speed, the oldest problem in the relations between human beings, and in the end the communicator will be confronted with the old problem, of what to say and how to say it. - Edward R. Murrow (1964)

  14. #74
    Community Member Loromir's Avatar
    Join Date
    Feb 2010
    Location
    Raleigh, NC
    Posts
    3,953

    Default

    Quote Originally Posted by Flavilandile View Post
    You're on a SSD Drive ?

    I didn't notice anything either...
    Except maybe a faster ability to move after loading when I change alts. I'll have to make more checks tonight.
    I'm on a plain jane vanilla hard drive. I set my number to 4,000...saw no difference in Load times or zone changes.

  15. #75
    Founder & Hero cdbd3rd's Avatar
    Join Date
    Jan 2006
    Location
    Escaping Mizzery in the Tavern Attic.
    Posts
    25,730

    Default

    Quote Originally Posted by sebastianosmith View Post

    My only remaining question would be what, considering that some who have reported significant performance increases are not mistaken, is causing the auto-detect routine to supply a value other than that 128 "sweet spot" which I think is the default....

    Wouldn't this be the same as the advantages of setting your own cache size, virtual mem setting, etc? Making the OS think (especially Windows) can confuse it.

    You know, technically speaking & all.
    CEO - Cupcake's Muskateers, Thelanis
    DDO Freebies

  16. #76
    Community Member YoureDown's Avatar
    Join Date
    May 2011
    Location
    Haifa, Israel
    Posts
    184

    Default

    Quote Originally Posted by Mindos View Post
    Find your userpreferences.ini file, usually located in My Documents, Dungeons and Dragons something, etc.

    Open it and scroll down to NET

    Input your own number for ConnectionSpeed.

    Note that the numbers here are very low, like very. I have a 30Mb cable line and put 5000 there with no problems.

    Discuss.
    setting to 5000 made a huge difference! (I'm testing higher numbers (First to try: 10k, since it seems to work great for me in other programs that support it) atm to see how it works and checking whether there are drawbacks of any description (except for the obvious slower internet speed in any other application))
    If you are seeing this the chance of there being a pony reaction gif up above is 73.42619%. In case there is none, please notify me and I will deliver a pastel colored equine to this thread.

  17. #77
    Community Member Shinjiteru's Avatar
    Join Date
    Jul 2010
    Posts
    192

    Default

    Ok, since this thread is around for a while now this is not treated as exploiting or using 3rd party tools or whatever.

    So... about if it is bad for the servers if all players would change this value... either Turbine doesn't know what this setting is doing or it can not harm the servers. Or maybe they are trying to find the developer who implemented this or still investigating the code responsible for this setting now.

    Ok... some said they see large numbers now in net status thingy while logging in, what dimension of large are we talking about here? several thousand, several million? Maybe a value what you are seeing in the mabar dragon instance?

  18. #78
    Community Member Arianka's Avatar
    Join Date
    Apr 2013
    Posts
    469

    Default

    No reason to set it above 2048 as MTU sizes for most routers is between 1450 and 1500.

  19. #79
    Community Member YoureDown's Avatar
    Join Date
    May 2011
    Location
    Haifa, Israel
    Posts
    184

    Default

    Quote Originally Posted by Arianka View Post
    No reason to set it above 2048 as MTU sizes for most routers is between 1450 and 1500.
    Most. not for those who have an insane highest teir router in place. seriously, I went overboard with it. (may be because my network is also hosting a big website for my family's company)
    If you are seeing this the chance of there being a pony reaction gif up above is 73.42619%. In case there is none, please notify me and I will deliver a pastel colored equine to this thread.

  20. #80

    Default

    Quote Originally Posted by cdbd3rd View Post
    Wouldn't this be the same as the advantages of setting your own cache size, virtual mem setting, etc? Making the OS think (especially Windows) can confuse it.

    You know, technically speaking & all.
    Well, you'd think that a setting of 0.00 or "Auto-Detect" would either fetch the actual connection speed from the OS or run some sort of test to determine it. If people are really seeing performance gains by tweaking it out to a ridiculously high number, what is preventing the client from finding the best possible value? If it's getting the connection speed from the OS, what value is it using? For various reasons many wireless NICs will connect to an 802.11g network at less than 54Mbs. If the client is plugging in a "54 or less" number, that's a problem because the scale is off by an order of magnitude. I'm quite curious as to what is going on if the, admittedly, anecdotal data are true.
    The newest computer can merely compound, at speed, the oldest problem in the relations between human beings, and in the end the communicator will be confronted with the old problem, of what to say and how to say it. - Edward R. Murrow (1964)

Page 4 of 5 FirstFirst 12345 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload