pdmlink speed connection

[ANDREALITTO]

Good morning, I have this problem:
we are an external office and communicate with a company using pdmlink, at the end of each job we check-in, unfortunately for connection problems the job we always do it outside the pdm. We use the wildfire 4 m170. we have a network of 1gb, the connection is very slow we use about 15\20 minutes to check-in of each part on average we have 200 parts for which at least 60 hours continuous connection. no one has been able to give us a hand all tell us that it is normal. I ask you, is it true? Can anyone help me? Thank you.

 

[Parametric_Ozzy]

I guess you don't have a replica server.. .

 

[ANDREALITTO]

Could you be clearer? what does it mean to have a replica server?thanks anyway for the immediate response

 

[Parametric_Ozzy]

First of all, write in the minuscule, if you write in the press in the forums is to shout, in theory you should also present yourself.

coming to your problem, I will try to explain it very briefly:

the company to which you are connected hosts the master site (main server) where there is complete installation of windchill pdmlink, database and ldap server as well as vaults.
the replication site (file server) hosts the installation of windchill and also all vaults and vaults replicated by the main server, but does not host the installation of the ldap database and server.
What does that mean?
data is replicated from the main to the server file and synced from the server file to the main server during replication sessions, while metadata always resides on the main server.
users of the server file in this way benefit from the speed of the local network instead of charging on the grop all data.

windchill (the 9.1) uses a system called site proximity to manage replication sources, meaning that each replication server requires data to the nearest server geographically, tricking it if it is main or file servers, as they are synchronized as mentioned above, this greatly speeds the activities.

the increase in performance is perceived in loading operations, then in check-in, but also check-out downloading, while other operations since they have to deal with the database where metadata is hosted do not have speed increases.

bottleneck at the end is always the upload speed of the local network.:smile:

I hope I explained. . .
greetings

 

[ANDREALITTO]

ok thank you so much, excuse for the writings in capital but I am not a praricante of the forums, however thanks to the tip, moreover I did not introduce myself to the second answer as I was the same of the first.
greetings

 

[Parametric_Ozzy]

ok thank you so much, excuse for the writings in capital but I am not a praricante of the forums, however thanks to the tip, moreover I did not introduce myself to the second answer as I was the same of the first.
greetings

I know you were the same, because I was referring to the first message. :wink:
what version of winchill used?

 

[ANDREALITTO]

currently we are using version 9.0, is there a higher release version that can help us?
Thank you.

 

[Parametric_Ozzy]

currently we are using version 9.0, is there a higher release version that can help us?
Thank you.

as I told you, it is not so much a version problem but of architecture.
with 9.1 but as said there are improvements in terms of geographical replications.
windchill 10 soon came out.

 

[mitch.]

It's been a long time since your message and so I hope you have solved your problems, however if you may be useful there are some parameters of the config file that help a lot in optimizing file transfers with remote pdmlink clients.

 

[goodwin]

would be interested to know what parameters are in the config.pro file for "some parameters of the config file that help a lot in optimizing file transfers with remote pdmlink clients."

Thank you very much

 

[mitch.]

are in particular two parameters to configure:
dm_upload_objects explicit (for those who work on the local network you can set up automatic)
in this way when I save in the avoided proe to transfer on the server side workspace files.
to charge them you must carry out the operation manually.

the other even more important parameter to set is:dm_http_compression_level 9 (configurable value from 0 to 9)
is the compression level of files in the transfer between the client and the server.
it is necessary to do some tests to verify what is the best value for your connection.

 

[goodwin]

Thanks again.
I'll do the tests as soon as possible.