www.Rivin.de :: Thema anzeigen

Caching
The autodownloader supports three levels of caching: None, Memory, and Full. These are detailed below.

None
This is set by using the following entry in nwn2player.ini:
CachingStrategy=0
This option is the most secure, as it will force NWN2 to fully scan every required file several times during the download process: when the client first connects, again after any required downloads are completed, and yet again when the player chooses or creates their PC. No results are cached on the player's machine, not even in-memory. However, this comes at a price: if you have a lot of files, or any large files, it means the player must wait for all of these scans to finish every time they log in - even if they disconnect and reconnect.
 This option is recommended only if you have a very small module - -less than 100MB, including hak paks.

Memory
This is set by using the following entry in nwn2player.ini: CachingStrategy=1
This option is a compromise between “None” and “Full”. The first time a player attempts to connect, all required files are fully scanned for updates. These results are kept in the client's memory; subsequent scans will first check this in-memory cache against the local files, to determine if the files have been modified. Memory cache is erased when the client is exited, either by crashing or closing normally. Disconnecting and reconnecting to your server does not clear the memory cache. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used.
 This is the minimum cache setting recommended, and is the default setting used.

Full
This is set by using the following entry in nwn2player.ini: CachingStrategy=2
NWN2: Autodownloader Server Admin Guide
Marc Paradise & Rob McGinnis
Last Modified: Apr. 07, 2009 3:44 PM
Obsidian Entertainment
Page 7 of 9
Full caching provides the ideal experience for your players and as such is the recommended configuration. Once files are verified, the results of that verification are cached and saved to the player's machine in an encrypted file. These cached results are used in subsequent checks to determine if players have modified their copy of the files. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used.
This is the cache setting recommended for most PW servers.

Autor:	Mirabell [ Fr 18. Feb 2011, 20:12 ]
Betreff des Beitrags:	Re: Downloader
Ich wundere mich eher gerade, warum ich fast 800 MB runter laden muss, also alle kompletten Rivin-Dateien, die ja ansich schon auf meinem Rechner sein sollten? Ziemlich heavy.

Autor:	Janald [ Fr 18. Feb 2011, 20:18 ]
Betreff des Beitrags:	Re: Downloader
Die PWC werden nun anders gespeichert. Daher müssen die Gebietsinformationen alle neu runtergeladen werden. Das sind nunmal 875 MB. Auch ein grund, warum das einloggen solange dauert, weil er bei jedem einloggen in alle dateien schaut ob sie noch aktuell sind

Autor:	Animus [ Fr 18. Feb 2011, 20:47 ]
Betreff des Beitrags:	Re: Downloader
Mein kleiner Bruder (selbst interessierter Scripter) hat mich letztens gefragt, warum wir nicht einfach jedesmal eine Textdatei mit der Versionsnummer mitsenden lassen und im ersten Schritt nur diese prüfen, um zu schauen ob etwas runtergeladen werden muss. Könnte man das nicht so einrichten?

Autor:	Loki12345 [ Sa 19. Feb 2011, 16:10 ]
Betreff des Beitrags:	Re: Downloader
ein kleiner Auszug aus dem Admin Guide für den Autodownloader: Zitat: Caching The autodownloader supports three levels of caching: None, Memory, and Full. These are detailed below. None This is set by using the following entry in nwn2player.ini: CachingStrategy=0 This option is the most secure, as it will force NWN2 to fully scan every required file several times during the download process: when the client first connects, again after any required downloads are completed, and yet again when the player chooses or creates their PC. No results are cached on the player's machine, not even in-memory. However, this comes at a price: if you have a lot of files, or any large files, it means the player must wait for all of these scans to finish every time they log in - even if they disconnect and reconnect.  This option is recommended only if you have a very small module - -less than 100MB, including hak paks. Memory This is set by using the following entry in nwn2player.ini: CachingStrategy=1 This option is a compromise between “None” and “Full”. The first time a player attempts to connect, all required files are fully scanned for updates. These results are kept in the client's memory; subsequent scans will first check this in-memory cache against the local files, to determine if the files have been modified. Memory cache is erased when the client is exited, either by crashing or closing normally. Disconnecting and reconnecting to your server does not clear the memory cache. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used.  This is the minimum cache setting recommended, and is the default setting used. Full This is set by using the following entry in nwn2player.ini: CachingStrategy=2 NWN2: Autodownloader Server Admin Guide Marc Paradise & Rob McGinnis Last Modified: Apr. 07, 2009 3:44 PM Obsidian Entertainment Page 7 of 9 Full caching provides the ideal experience for your players and as such is the recommended configuration. Once files are verified, the results of that verification are cached and saved to the player's machine in an encrypted file. These cached results are used in subsequent checks to determine if players have modified their copy of the files. The only exceptions to this are resources marked as “critical” - they will always be fully scanned no matter which caching option is used. This is the cache setting recommended for most PW servers. kann es sein, das wir diese Cache Einstellungen ändern müssen? Jedenfalls kommt mir das Verhalten des Downloaders im Moment so vor, als stünde er auf "none" bzw. CachingStrategy=0.

Autor:	Janald [ Sa 19. Feb 2011, 16:43 ]
Betreff des Beitrags:	Re: Downloader
Genau das habe ich weitergegeben. ich tippe auf die standard einstellung, also die 1. Denn wenn man schon einmal eingeloggt war geht es definitiv schneller. Mal schauen was Eldon daraus macht

www.Rivin.de https://www.rivin.de/forum/

Downloader https://www.rivin.de/forum/viewtopic.php?f=19&t=5666	Seite 2 von 2

Autor:	Loki12345 [ Sa 19. Feb 2011, 17:36 ]
Betreff des Beitrags:	Re: Downloader
Naja, bei uns nicht wirklich Also bei Merke und mir. Edit: Ok, bei Merke heute für ein Update von ca. 5.93mb nur für das überprüfen auf Aktualität 11.30 gebraucht. CPU: Athlon 64 3700+ Ram: 1.5 GB Bei mir: 3.30 min CPU: Athlon 64 3700+ Ram: 2GB

Autor:	Eldon [ Mo 21. Feb 2011, 15:37 ]
Betreff des Beitrags:	Re: Downloader
Ich habe die Konfiguration von CachingStrategy=1 auf CachingStrategy=2 geändert. Damit sollte es nur noch zu Verzögerungen kommen, wenn wir wirklich ein Update durchgeführt haben.

Autor:	Janald [ Mo 21. Feb 2011, 15:48 ]
Betreff des Beitrags:	Re: Downloader
Klappt ausgezeichnet. Hab gestartet, dann NWN 2 ausgemacht, damit die Daten aus dem Cache verschwinden und wieder angemacht. Läuft wunderbar durch. Und bevor die ersten Beschwerden kommen es sei gar nicht schneller: Beim erstenmal wird es noch sein wie immer, da erst dann eine Datei angelegt wird in der sich NWN 2 merkt, dass es aktuell ist. Erst nach dem ersten einloggen sollte es also besser sein. Danke Eldon

Autor:	Animus [ Di 22. Feb 2011, 04:20 ]
Betreff des Beitrags:	Re: Downloader
Eldon, ich liebe dich! Willst du mich heiraten?

Autor:	Loki12345 [ So 27. Feb 2011, 22:53 ]
Betreff des Beitrags:	Re: Downloader
Eldon, du bist der Beste. Funktioniert nun rasend schnell und tadellos, vielen Dank dafür.

Seite 2 von 2	Alle Zeiten sind UTC + 1 Stunde [ Sommerzeit ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/