No parts of this manual, in whole or in part, may be copied, photocopied, translated, or transmitted to any electronic medium or machine readable form without the prior written permission of FLIR Systems, Inc. This accounts for user-initiated manual syncs.1 United VMS 8.0 Release Notes Rel Latitude / Horizon / Meridian Ver. Sharing a file in a Net Folder, flags the folder for synchronization at the next sync interval, thus affecting all users assigned to the Net Folder. Uploading a file to a Net Folder, flags the folder for synchronization at the next sync interval, thus affecting all users assigned to the Net Folder.ĭeleting a file from a Net Folder, flags the folder for synchronization at the next sync interval, thus affecting all users assigned to the Net Folder. Updating a file in a Net Folder, flags the folder for synchronization at the next sync interval, thus affecting all users assigned to the Net Folder. Renaming a file in a Net Folder, flags the folder for synchronization at the next sync interval, thus affecting all users assigned to the Net Folder. Rename a file in My Files or a Net Folder The update frequency was set 50% higher than the upload frequency because testers assumed that users edit and update files more frequently than they create and upload them.īy the same token, testers assumed that it’s far more common for users to edit and do other work in their My Files/Home Directory areas than it is in Net Folders.Ĭomment on a file in My Files or a Net FolderĬomments logged in a Net Folder flag the folder for synchronization, thus affecting all users assigned to the Net Folder. Table 1 Filr-Active Desktop Profile ActivitiesĬheck for Net Folder synchronization flag Novell testing utilized a test bed with the components illustrated in the following graphics. Following the recommendations in the Novell Filr 1.1 Planning and Deployment Best Practices Guide, and sizing the system so that it can adequately scale according to requirements, will ensure a successful Filr deployment. Filr administrators can use the results presented for extrapolation when planning their own Filr deployment. This white paper describes the methodology used by Novell in testing Filr 1.1 scalability, as well as the scalability test results and findings. There are obviously other factors too, such as host server hardware used, available RAM, network bandwidth, database back-end performance etc. It’s important to remember that the actual workload capacity is a function of the number of user activities, not the number of Filr users. The workload was optimized by monitoring CPU usage and keeping system response times at a reasonable level.Depending on the activity workload that an organization’s users generate, a Filr deployment similar to the test bed used in our scalability testing would be able to serve between 10 users. The actual number of users or files are not necessarily the most important factors when it comes to scalability, but rather the level of activities performed by the users of the Filr system.Novell Testing measured Filr’s activity-workload-handling capacity by gauging the effect that different file-related user activities had on the test bed illustrated below in this document. The workload-activities are generated by Filr clients sending requests to the Filr virtual appliances. To plan an optimal Filr deployment, administrators need information about Filr’s activity-workload-handling capacity.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |