Есть сетка гигабинтая из 20 машин в

[paolo 0]

сборки по пол часа.

Машины мощные. Есть файл сервер откуда они их тянут.

Ге исакть траблы на конкретных локальных машинах или акто оптимизировать сервак?

[SVB 188]

Не зная конкретных хорактеристик сервака, сборок и персональных машин трудно дать однозначную рекомендацию. Можно лишь отметить с высокой степенью правдивости: so so.

[paolo 0]

Клиенты P3 1000 по 1 Г оперативки, 1 Г сетевухи, карты Ge force 2 GTS (это самое слабое)

Сервак 2 процессорный,120 Гигов сказевых, RAD HAT.

Правда сейчас свободных всего 3 гига.

[SVB 188]

2paolo

Вы не упомянули какая платформа сервака: Wintel или UNIX. Все-таки сервак на юниксе можно сделать заметно более производительным. Нам PTC советует именно такой путь, правда идет разговор о Windchill а не просто о Pro/E. На первый взгляд и персоналки у Вас не ахти какие. Правда я не понял какие конкретно у Вас сборки (это очень важно), сколько занимают места в ОП? Какой чипсет у персоналок? Какой тип памяти с какими характеристиками? Похоже что горлышко Вашей "бутылки" - гигабитные сетевухи заметно шире (производительней) Ваших емкостей - сервака и персоналок.

Изменено 14 ноября 2003 пользователем SVB

[Half 0]

Провел сейчас эксперимент:

Сборка из 122 объектов (117 файлов общим объемом 27,4Мб) втягивалаь с сервера PIII-600/512 c 20 GB UDMA66 винтом по 100Мб сетке за 37 секунд (с учетом регенерации двух несложных Instance)

Все это проводилось через Pro/Intralink (клиент сейчас PIV-3000/1000 с SerialATA винтом)

Может у вас с сетью проблемы (коллизии там всякие)?

Или может вы все на работу в одно время приходите, и начинаете файлы тянуть...

[paolo 0]

В том то и дело что все приходят в одно время и начинают тянуть сборки.

Но есть одно но.В выходные когда сидит 1 или 2 сотрудника заметного прироста нет производительности. Поэтому мне и кажеться что это что то в настройках Pro/e или машины слабоваты.

Сборка размером 13 метров может грузиться 20 минут

[Aleksandr 1]

А если не с сервера, а с конкретного компьютера грузить, то сколько времени уходит?

[Half 0]

Это скорее в настройках сети - это вам к Администратору

А может у вас Family Table много, а они при загрузке регенерятся...

[al264 0]

Вы не упомянули какая платформа сервака: Wintel или UNIX

Человек же ясно написал -RAD HAT, в смысле RedHat . Pro/E скорее всего ни при чем, сеть надо проверить.

Закачать ту же сборку по FTP.

[SHARit 2 808]

Присоединюсь к вопросу Aleksandr

А если не с сервера, а с конкретного компьютера грузить, то сколько времени уходит?

Прежде чем вскрывать проводку, может лампочку проверим.....

[Aleksandr 1]

Конфиги-то поди на всех машинах одинаковые. Может в нем что-то наворочено.

[paolo 0]

Завтра в субботу проверю.Когда никого не будет.Спасибо. Жду дальнейшей помощи.

[Half 0]

Еще внесу свою лепту

Suggested Technique for Improving Retrieval Performance

Through The Network.

1. Settings in the config.pro

config.pro option

value

comment

TRAIL_DIR /tmp or c:\temp

This option will make Pro/ENGINEER create the trail file in the directory specified. Specifying a local directory, such as /tmp, will avoid network access.

USE_TEMP_DIR_FOR_INST yes

This option will make Pro/ENGINEER use the directory specified by the TMP or TEMP system variable to create temporary file while retrieving instances.

It is important to set these system variable correctly to /TMP or /tmp for UNIX; TMP c:\temp or TEMP c:\temp for Windows

See also

TPI 21133 "How To Speed Up the Retrieving of a Model With Family Table From a Shared Network Drive or a Mounted Directory" , 

SEARCH_PATH or SEARCH_PATH_FILE directories in which Pro/ENGINEER models are stored.

Pro/ENGINEER will search in every directory listed in the SEARCH_PATH (or in the search.pro file) until it finds the correct model. Therefore, the retrieval time is highly impacted by the number of search paths set up in search.pro or config.pro.

For these reasons, it is important to have as few SEARCH_PATH statements or as short a search.pro file as possible with as few objects as possible per directory.

If it is not possible to remove libraries from these lists, it is important to have the search paths listed in the most efficient order as possible.

See also TAN 101321 "On NT Machines, Retrieval Time is much more Longer while Using SEARCH_PATH Than When Retrieving Models from a Single Directory"

--------------------------------------------------------------------------------

2. Network settings

Even if a file server is used to store the Pro/ENGINEER models onto the network, it is more efficient to have a local installation directory of Pro/ENGINEER, to improve the Pro/ENGINEER starting time, as well as a local starting and working directory.

DNS

If DNS is used, try the following command from the client machine: ping <dns server ip address>. If the return time is too long, this can show a problem on the network. (a normal respond time will be <10ms on a 10 Mbyte Local Area Network)

Client/Server Communication

Examine the time returned by ping <file server>, ping <license server>, if these times are too long, Pro/ENGINEER will take longer to execute. (The same respond time should be obtained as for the test with DNS)

Network nodes

Considering the architecture of the network, it could be useful to know how many hubs there are between the client and the server. Ideally, this number should be less than 4).

Is it hub or switch network?

If switches are used, make a test locally with a simple hub between two machines to determine if any of the switch settings are impacting the network performance.

Network topology

Which network topology is used? Only Ethernet networks are supported.

--------------------------------------------------------------------------------

3. UNIX specific settings.

NFS settings.

When using NFS to mount directories from a server to a client, some options should be set to improve performance. It is important to contact the hardware vendors to tune the network. These settings can change depending on the workstation model and the OS release.

However, it will always be better to use a hard mount instead of a soft mount. This will avoid data loss if the NFS connection is interrupted.

In addition to this, the version of the NFS software being used is important. The performance improvement between two versions is very often significant, but can only be measured by tests

This setting can usually be changed using the option of the mount command:

example: mount -o vers=2,hard server:/path_to_dir /path_to_local_dir ( ver=2 gives the version of NFS to use)

--------------------------------------------------------------------------------

4. Windows NT specific settings.

Network protocols and services:

The Network properties (#Control Panel\#Network) should have the following protocol and services listed:

Protocols: NETBEUI, TCP/IP. (Note: NetBEUI is not a suitable protocol for networks with more than 200 machines)

The TCP/IP protocol should be configured with a fixed ip address, a subnet mask, and a default gateway.

In the DNS folder, the setting should refer to existing DNS servers (if any are configured).

If the DNS servers cannot be pinged, remove them. The DNS domain (if one is set) should exist in the network and must be able to be pinged.

Services: The network services should be: Interface NETBIOS, Server, Workstation, RPC configuration, computer Browser, simple TCP/IP and, eventually, Microsoft TCP/IP Printing.

Bindings: One of the most important thing on a Windows network is to configure the bindings in the following way: for all services listed (Netbios Interface, Server and Workstation) the NETBEUI protocol MUST be placed in first position before WINS TCP/IP. See also TPI 20297 "Retrieval of Models in Pro/ENGINEER is Significantly Slower than to be Expected"

These settings should be made on both the server and the client machines.

If other protocols and services are listed (like IPX/SPX, nwlink netware, etc.), a test should be made without these additional protocols to control the impact on Pro/ENGINEER performance.

File system: FAT or NTFS.

The Pro/ENGINEER installation directory, the starting directory, the working directory, and the directories in which Pro/ENGINEER data are stored must be NTFS formatted.

Services

In #Control Panel\#Administrtive Tools\#Services, check to see if any extra services are running, such as Network sniffer, antivirus, etc. It is good practice to stop extra services to test if they are affecting Pro/ENGINEER performance. For example, an antivirus software which checks the incoming and outcoming files on the server will dramatically increase the retrieval time into Pro/ENGINEER. Configuring it to check only the incoming files will improve retrieval performance.

Number of files per directory and long filename:

Due to a Microsoft issue, if there is a large number of files in one directory or filenames with 20 characters or more are present, retrieval time may be longer. A registry key can be added to address this issue. See <noindex>http://support.microsoft.com/support/kb/ar...s/Q177/2/66.asp</noindex>

Number of mapped network drives.

The performance of Pro/ENGINEER can be impacted by the number of mapped network drives on the machine. This impact can be important if some mapped drives are no longer accessible. A test should be made by disconnecting every mapped drive.

Retrieving files on a Windows NT server on a Windows 2000/XP client:

Due to a Microsoft issue, retrieving files located on a Windows NT server from a Windows 2000/XP workstation is slow. A registry key can be edited to address this issue. See <noindex>http://support.microsoft.com/default.aspx?...kb;EN-US;279282</noindex>

Additionally, see the related articles:

Взято <noindex>Отсюда</noindex>

[suslad 1]

Какие протоколы используются?

Адреса клиентов статические или динамические?