• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

velocità apertura assembly in win10

  • Thread starter Thread starter ApeGana
  • Start date Start date

ApeGana

Guest
Bye to all,
I have a strange problem with the last 2 pcs purchased in my company, so I don't know where to put my hands.
we have 5 pcs in which it is installed solid edge st8, are machines with heterogeneous hardware but of good level, all quite recent (the oldest is 3 years); 3 of these have win7, the last 2 win10.

I installed st8 a few days ago on the last car delivered, it seemed to work well...
Today I realize a strange slowness on one of these in opening a relatively simple assembly; I do some proof and I see that the particularly long time is the one used to read the various par and psm of which the asm is composed.
takes 22 seconds to open an assembly with only a 40ine of pieces, it seems to me an eternity, I try on my pc (the oldest of the office) and it takes 4 and a half seconds.
I also begin to try other axioms and see that more or less all are affected and that the problem is similar also in the other pc with win10 and instead does not exist on those with win7.
on the other hand I also found assemblies with many pieces that instead charge very quickly!

I did dozens of tests, activating and deactivating antivirus, firewall, uac, network permissions...., some testing on the wall....

In the end I think I have understood the problem: in the opening of the axieme, the loading phase of the par or psm files (or even subassiemi asms) is incredibly slow when they are inside folders that contain many files (I mean from 1000/2000 up). I don't have any more doubts about this.

actually then known that even banal windows operations seem to slow down in such folders (type create a new text file and then delete it). but only in the pcs with win10!

among other things only one of the 2 pcs with win10 is new (they gave it to me 4 days ago); The other one we have for five months and I have a colleague who works there every day, and it seems impossible that until now he has noticed nothing.

synthesizing:
  • Did anyone else notice anything like that?
  • possible there has recently been an update of win10 that gives rise to this problem?
  • Does any good soul have any idea how I can solve the problem?
Thank you.
... and apologize for the length of the post.

Matteo
 
I solved.
I describe briefly for the benefit of any users who may be in the same situation.

the problem was due to the activation of a feature on our server (so: windows server 2012 r2); This feature is called "access-based enumeration" (abe), and was activated in the context of a revision of access permits to the various folders to make sure that those who do not have read access to a folder do not even see it.

this enabled option originated in PCs with windows 10 (d. 1803) to the problem described in highly populated folders.

We disabled the bee.

Bye.
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top