2016 VISO威驰合作方案 (讲义NXPowerLite

VISIO 培训课程一、VISIO的基本操作界面及功能 (3)二、模板与模具的选择 (4)三、模具主要内容介绍 (6)1.建立一个新的跨职能流程图 (6)2.修改与变更原有的跨职能流程图 (9)3组织结构图 (12)四、图形 (19)1图形的创建 (19)2图形的移动 (19)3同时移动多个图形 (19)4图形的删除 (20)5图形格式修改 (20)五、文字表述 (21)1新增或修改文字 (21)2文字格式的修改 (21)六、连线 (24)1连线的创建 (24)2连线的格式 (26)3编辑连线上的文字 (28)七、组合 (29)1如何建立组合 (29)2取消组合 (31)八、页面 (32)1页面增加 (32)2页面设置 (33)3页面移动 (34)4使用背景 (36)5删除页面 (37)6页面命名 (37)九、超链接 (38)1文件内 (38)2WORD (39)3EXCEL (41)十、打印 (42)1打印范围及份数设置 (42)2将一页分为多页打印 (43)一、VISIO的基本操作界面及功能以下是VISIO的基本操作界面：•A表示菜单和工具栏，使用方法同word和excel。

•B在打开页面时，会出现最适当的尺寸、方位、比例、格线以及刻度等。

•C点选工具栏上按钮旁边的下拉箭头时，会出现与该钮有关的工具。

•D可以利用格线来把图形排列整齐。

• E 当鼠标指向工具栏上的按钮时，会在旁边出现一个说明，显示该按钮的功能。

• F 页面左侧表示模具中预设的图形。

•G 在页面标签列中，您可以快速地新增、删除、更名或排序页面，按下鼠标右键即可选择。

•H 当鼠标指向左边功能区上的图形时，会出现该图形的说明。

•I 如果档案包含很多页，您可以利用下方的水平卷动轴来阅览所有的页面。

接着，我们将对VISIO的功能及使用做更详细的说明。

二、模板与模具的选择在Visio 2002中，可以用现成的模板来完成您想要制作的成品，其方法如下：1.打开VISIO，会出现如下画面：2.只需用鼠标双击右侧预览区中的模板，便能打开模板，接着会出现全新的页面以及一些模具。

安裝指南:Nintex for SharePoint2016最後更新日期2016年8月9日法律聲明若要瞭解最新資訊，請參閱/company/legal。

目錄簡介1工作表(可選)1安裝檢查清單1安裝工作表1Nintex工作流程與Nintex表單2快速安裝1執行安裝程式並匯入授權檔1部署Nintex工作流程企業解決方案(可選)1設定資料庫1啟動網頁應用程式2設定Nintex工作流程電子郵件設定2啟用外部功能(可選)2啟用Nintex工作流程動作3在SharePoint中啟動功能3計劃測試和生產的環境3系統需求3檢視拓撲細則與最佳實務4高可用性4容量考量4儲存空間4內容資料庫與效能4SharePoint和SQL Server5安全性5備份和恢復5資料庫對應5同時進行備份和還原5SharePoint和SQL Server6設定安裝拓撲6確保服務正在執行6停用防毒軟體7設定用於執行安裝程式的伺服器7安裝Nintex產品以測試環境並確認8安裝Nintex產品至生產環境8取得具有足夠權限的帳戶8用於Nintex安裝的典型帳戶8所需的最低權限9取得Nintex授權檔9安排部署9執行安裝程式10 Nintex安裝程式10匯入授權檔10部署解決方案步驟11設定資料庫與其他項目11 Nintex產品設定11為Nintex工作流程和表單設定資料庫12啟動網頁應用程式13啟用Nintex工作流程動作14設定SharePoint電子郵件的先決條件14設定Nintex工作流程電子郵件設定15設定LazyApproval15連接並啟用外部連結和外部表單功能17啟用基於表單的Nintex Mobile驗證19啟用「外部啟動」19在SharePoint中啟動功能20確認產品安裝21測試Nintex功能21確認安裝程式及設定工作(可選)22 Nintex組件與功能22解決方案部署22授權22資料庫23已啟用的動作(安全控制項)24恢復原始伺服器設定24附錄24 Nintex Workflow Exchange Connector Service安裝24簡介24系統需求24安裝Nintex Workflow Exchange Connector Service24完成安裝後工作25從Nintex工作流程連接Exchange27手動匯出和匯入Nintex產品和解決方案28部署解決方案29解決方案與所需部署29解決方案部署的順序29解除安裝Nintex產品30若您計劃重新安裝Nintex平台30完全解除安裝30簡介本文件為安裝SharePoint2016Nintex提供指引。

奥美策略全集 NXPowerLite精品课件(一)作为一名教育工作者，我们时常面临的一个问题就是漫长的电子课件。

有时，我们需要向学生们展示一些很有意义的幻灯片或者课件，但是由于它们太大，就会导致上传和下载速度非常慢，这会给我们的教学带来很大的麻烦。

然而，现在我们不用担心这个问题了。

奥美策略全集 NXPowerLite精品课件是一种非常棒的解决方案，通过压缩课件中的图片和媒体文件，它能够显著减小课件的大小，从而使上传和下载速度大大提高。

下面是一个简要介绍：NXPowerLite是一种非常高效的压缩器，使用它可以将PowerPoint、Word和Excel文档的大小减少95%以上。

它特别适用于那些包含大量图像、表格和嵌入式媒体文件的文件。

与此同时，压缩后的文件不会丧失任何质量和内容，提高了文件传输的速度和效率。

奥美策略全集 NXPowerLite精品课件涵盖了从语文、数学、英语到物理、化学等多个学科领域的优秀课件，课件具有丰富的内容和精美的演示效果，非常适合教师们使用。

使用奥美策略全集 NXPowerLite精品课件有许多好处。

首先，它可以大大提高文件的上传和下载速度。

这意味着你可以更快、更轻松地与学生分享你的课件，而不必担心它们在上传或下载过程中被损坏或丢失。

其次，奥美策略全集 NXPowerLite精品课件不仅压缩了媒体文件，也压缩了PowerPoint、Word和Excel文件中的其他内容。

这意味着你可以在文件大小和内容之间取得平衡，从而获得最佳的效果。

最后，奥美策略全集 NXPowerLite精品课件也可以让你在手机、平板电脑或其他便携设备上查看你的文件，无论你是否联网。

这使你可以随时随地查看和编辑你的课件，从而更加灵活地进行教学。

总之，奥美策略全集 NXPowerLite精品课件是一种非常有用的工具，对于那些经常需要上传或下载大型文件的教育工作者来说尤为适用。

通过使用这个工具，你可以轻松地减少文件的大小，从而提高文件传输的速度和效率，使你的教学更加高效、便捷和灵活。

Visio与团队协作和共享绘图技巧Visio是一款功能强大的绘图工具，被广泛应用于各个领域的团队合作中。

在日常的工作和项目中，团队成员需要频繁地进行绘图和图表的制作，而Visio提供了丰富的协作和共享功能，能够有效提高团队的工作效率和合作能力。

本文将探讨如何利用Visio进行团队协作和共享绘图，让团队成员更好地协同工作。

一、创建和管理共享绘图1. 创建共享绘图文件在Visio中，可以选择创建共享绘图文件，以便团队成员可以同时进行编辑和访问。

在创建共享绘图文件时，需要设定共享权限和访问方式，确保团队成员可以根据需要进行编辑和查看。

2. 管理共享绘图权限在Visio中，可以设定团队成员的权限级别，以控制对绘图文件的修改和编辑。

根据项目或者团队的需要，可以设置不同的权限级别，例如只读、编辑、修改等，确保绘图文件的安全和完整性。

3. 版本控制和追踪在团队协作中，经常出现多个人同时编辑同一个绘图文件的情况。

Visio提供了版本控制和追踪的功能，可以记录每一次修改和编辑，方便团队成员了解绘图文件的变更情况，并可以回溯到之前的版本。

二、共享和协同编辑1. 共享绘图文件链接在Visio中，可以创建共享链接，将绘图文件以链接的形式发送给团队成员。

通过共享链接，团队成员可以直接在浏览器中打开和编辑该绘图文件，无需下载和安装Visio软件。

2. 同时协同编辑Visio还支持同时多人协同编辑一个绘图文件的功能。

团队成员可以通过Visio Online或者Visio Online Plan 2订阅来实现多人同时编辑的效果，增强团队协作的实时性和效率。

三、使用共享绘图库1. 创建共享绘图库在Visio中，可以创建共享绘图库，将常用的图形和模板保存到服务器上供团队成员使用。

通过共享绘图库，团队成员可以快速访问和使用常用的图形元素，提高效率和一致性。

2. 更新和管理共享绘图库共享绘图库是一个动态的工具，需要不断更新和管理。

团队成员可以根据实际需要向共享绘图库中添加新的图形和模板，并对已有的图形进行修订和更新，确保绘图库的完整和有效性。

visio 2016标准版
Visio 2016标准版是微软公司推出的一款专业的流程图和图表设计软件。

它为用户提供了丰富的图形库和工具，可以帮助用户轻松地创建各种类型的图表、流程图、组织结构图、网络图、平面布局图等。

Visio 2016标准版具有以下特点和功能：
1. 丰富的图形库，Visio 2016标准版内置了大量的预定义图形，用户可以根据自己的需求快速拖放这些图形来创建图表和流程图。

2. 智能连接，软件具有智能连接功能，可以自动对图形进行连接，帮助用户轻松创建复杂的流程图和网络图。

3. 数据连接，Visio 2016标准版支持与Excel、SQL Server 等数据源进行连接，用户可以将数据直接导入到图表中，实现数据驱动的图表设计。

4. 协作和共享，软件支持多人协作，用户可以轻松地与团队成员共享和编辑图表，提高团队的工作效率。

5. 自定义模板，用户可以根据自己的需求创建和保存自定义模板，方便以后的使用。

6. 导出和打印，Visio 2016标准版支持将图表导出为多种格式，如PDF、图片等，并且可以直接打印高质量的图表。

总的来说，Visio 2016标准版是一款功能强大、易于使用的图表设计软件，适用于各种行业和领域的用户，能够帮助用户快速、准确地创建各种类型的图表和流程图，提高工作效率和表现力。

T arun ChopraSr . Escalation Engineer Microsoft CorporationSharePoint 2016 Protocol OverviewObjective•Provide insight into the SharePoint protocol structure and the corresponding Open Specifications•Offer a high-level view of the SharePoint protocols as presented by the MS-SPO overview document•Connect product features in SharePoint with the corresponding Open SpecificationsAgenda•Introduction to SharePoint Server •Updates in Share point server ‘2016•Core Platform Protocols •Extended Capabilities Protocols •Example walkthrough •QuestionsIntroduction to SharePoint ServerCollaborateSitesSocialContentSearchInsights Composites Office Client and Office Web App Integration Ribbon UISharePoint WorkspaceSocial Relevance Phonetic Search NavigationEnhanced PipelineEnterprise Content Types Metadata and Navigation Document SetsMulti-stage DispositionAudio and Video Content Types Remote Blob Storage List EnhancementsTagging, Tag Cloud, Ratings Social Bookmarking Blogs and Wikis My SitesActivity FeedsProfiles and Expertise Org BrowserExcel Services Chart Web Part Visio Services Web AnalyticsSQL Server Integration PowerPivotBusiness Connectivity Services InfoPath Form Services External Lists WorkflowSharePoint Designer Visual StudioAPI Enhancements REST/ODATA/RSSSharePoint 2016 UpdatesSharePoint 2016▪Improved mobile navigation experience▪Simplified content creation, management & sharing ▪Improved search support▪Image and Video previews▪Encrypted connections(TLS 1.2)▪Zero downtime patching▪Fast Site CreationReference : https:///en-us/library/mt346121(v=office.16).aspxDeveloper LandscapeServer SDK Client SDKSharePoint &Office AppsSharePoint and Office Protocols REST/ODataSharePoint ProtocolsProtocols OrganizationSharePoint Products and T echnology ProtocolsMS-SPO(166 Protocols)SharePoint ProtocolsOverviewMicrosoft OfficeProtocolsMS-OCPROTO(75 Protocols)Office Client ProtocolsOverviewProtocol Architecture / T opologyMS-SPOSharePoint Protocols OverviewMS-OCPROTOOffice Client Protocol OverviewCore Platform ProtocolsExtended Capabilities ProtocolsOffice Client ApplicationsSharePoint Protocols OverviewSharePoint Protocols Overview [MS-SPO]▪Informative Overview of SharePoint Protocols▪SharePoint protocols are implemented using HTTP or extensions such as SOAP web services▪Covers communication between SharePoint Servers and Clients, and Applications/other Server Applications▪Organized by Core Platform and Extended CapabilitiesArchitecture –Web T opologyCore Platform Protocols▪Central Administration Site▪Create sites, users, collections, etc.▪Manage sites, users, collections, etc.▪UI Management▪Vertical capability managementCore Platform Protocols▪Site collections▪Sites, Lists, Libraries, documents, etc.▪Content typesExtended Capability Protocols(i.e. Excel Services)Logical Storage -Container Hierarchy Site CollectionsSitesLists and LibrariesFoldersList Items and Documents▪Site Administration ▪List Data▪File Operations▪Security and Identity ▪Authoring Integration ▪Extensibility▪Client-Side Object ModelSharePoint Core Platform ProtocolsSite AdministrationCore Platform Protocols•Manage Site Collections and Sites: MS-ADMINS, MS-WEBSS•Create or delete site collections and retrieve information about collections•Access and modify sites in the site collection•Manage Document Workspaces and Meeting Workspaces: MS-DWSS, MS-MEETS •Built from specific site definitions to target specific usage scenarios•Document Workspace sites facilitate the collaboration of multiple authors on a singledocument with supporting collateral•Meeting Workspace sites organizes content that is associated with a meeting (i.e. agendas, participants, follow-up details, and supporting collateral)List DataCore Platform Protocols•Access to Lists, Forms, Views, Schema: MS-LISTSWS, MS-VIEWSS, MS-FORMS, MS-WSSCAML, MS-WSSREST•Alerts: MS-ALERTSS, MS-OSALER•When and how notifications are sent to users when content is changed (subscriptions)•Outlook Sync: MS-OUTSPS, MS-STSSYN•Stores and synchronizes SharePoint lists with Outlook•Outlook also leverages MS-LISTSWSFile OperationsCore Platform Protocols•File access and management•Files and folders are available through WEBDAV, MS-FSSHTTP •Versioning MS-VERSS•Major versions, minor versions, & checked out versions •Described more thoroughly in the MS-OCPROTO documentAdditional Core Platform ProtocolsSecurity and Identity (Authentication)•Pluggable Authentication, Forms Based Authentication, Claims Authentication: MS-AUTHWS, MS-PEOPS, MS-OFBA, MS-CPSWS, MS-SPSTWS•Manage Authorization, Permissions, and Groups: MS-PERMS, MS-UGSAuthoring Integration•Supports authoring Blogs, Slide Libraries, Picture Libraries: MS-METAWEB, MS-SLIDELI, MS-IMAGS•File Synchronization and Coauthoring: MS-FSSHTTP , MS-FSSHTTPB, MS-SHDACCWSExtensibility•Support Content Import/Export: MS-SITESS, MS-CDEPLOY, MS-PRIMEPF•Workflow Integration and Group Approval: MS-WWSP, MS-EAWF•Web Page and Web Part Customization: MS-WPPS, MS-CONATBClient-Side Object Model•JavaScript and Managed API•Supports Batch Requests: MS-CSOM, MS-CSOMSPT, MS-CSOMRESTExtended Capabilities•Excel Services•Access Services•InfoPath Form Services•User Profile Services•Search Services•Business Connectivity Services •Content Management Services •Performance Point Services •Analytics Services•Office Online Web Query Service Publishing workbooks to SharePoint, Programmatic access to workbook contents, data accessPublishing and programmatic access to database applications on SharePointPeople, activity feeds (SharePoint actions, birthdays, etc.), social network scenarios, ratings, etc.Versioning, spellcheck, and records managementScenariosSharePoint Scenario 1Use of MS-LISTSWS to check-out, and check-in a file from a siteSharePoint Scenario 2Use of multiple protocols to create a new Site and access List data MS-SITESS▪Get information about a site or collection▪Create or Delete Sites▪Manage the site▪Retrieve T emplatesMS-WEBSS▪Read and update attributes of Sites▪Retrieve list templatesMS-LISTSWS▪List data managementFinal ThoughtsFinal Thoughts•Many options are available when developing with SharePoint; protocols are just one avenue•If you are currently leveraging the protocols, let us know after the talk•There are lots of resources to assist your protocol development (most are free)Q&ASharePoint Interoperability Resources▪Open Specification Learn Center▪/en-us/openspecifications/dd569930.aspx ▪Complimentary Support on Open Specifications▪*********************▪Customer events▪Microsoft Channel 9 –Recordings from previous events▪SharePoint protocol test suites▪Network parsersThank you !!。

TABLE OF CONTENTS Users Per Server (UPS) (1)Technology Overview (3)Autodesk Revit 2016 Application (3)NVIDIA GRID Platform (3)Software and Hardware Used in the Tests (4)Hardware Encoding with NVENC and VMware Blast Extreme (5)Testing Methodology (6)The Performance Engineering Lab (6)Recommended Revit Physical System Configuration (7)Typical Revit Workstation Builds (7)Autodesk Revit Benchmark Metrics (RFO) (8)Test Workloads (9)How the Tests Were Run (10)Test Limitations (10)Test Results (11)Test Threshold Times (11)GRID K2 Test Execution Times (12)Tesla M60 with NVENC Test Execution Times (12)Test Execution Times With and Without Hardware Acceleration (13)CPU Utilization Against GPU Utilization (14)Conclusion (16)The purpose of this guide is to give a detailed analysis of how many users organizations can expect to get per servers based on performance testing with the Autodesk Revit 2016. The NVIDIA Performance Lab worked in cooperation with the Autodesk team to determine the maximum recommended number of users for the reference server configuration. Testing for this guide is based on the industry-standard RFO benchmark to determine the maximum number of Autodesk Revit users per server (UPS) that NVIDIA GRID® can support. To provide customers with a reference point, we have included testing for the latest generation of NVIDIA GRID solution, NVIDIA GRID Virtual Workstation software on NVIDIA Tesla™ M60, as compared to the previous generation, GRID K2. Based on extensive testing, NVIDIA GRID provides the following performance and scalability recommendation.Figure 1 Autodesk Revit 2016 Users per Server for GRID K2 and Tesla M60Users Per Server (UPS) The maximum number of users per server is based on performance and scalability metrics for Autodesk Revit 2016 configured to perform high workloads concurrently while maintaining reasonable usability.AUTODESK REVIT 2016 APPLICATIONAutodesk Revit is Building Information Modeling (BIM) software with features for the following elements of building design and construction:④Architectural design④Mechanical, engineering, plumbing (MEP) design④Structural engineering④ConstructionWhen architecting your NVIDIA GRID environment for Revit, you must consider both the GPU and the CPU.④Revit requires a GPU as users rotate, zoom, and interact with drawings.④Revit creates a heavy CPU load as it manages all the elements of a drawing througha database.Because it uses a database, Revit needs high performance storage to functionproperly. The heaviest Revit CPU usage occurs during data-rich operations such as opening and saving files, and updating models.NVIDIA GRID PLATFORMNVIDIA re-defined visual computing by giving designers, engineers, scientists, and graphics artists the power to take on the biggest visualization challenges with immersive, interactive, photorealistic environments.NVIDIA GRID exploits the power of NVIDIA Tesla GPUs to deliver virtual workstations from the data center or the cloud. Architects, engineers, and designers arenow liberated from their desks and can access their graphics-intensive applications and data anywhere.The NVIDIA Tesla M60 GPU accelerator works with NVIDIA GRID software to provide the industry’s highest user performance for virtualized workstati ons, desktops, and applications. This solution allows enterprises to virtualize any application—including professional graphics applications—and deliver them to any device anywhere.Since its first release in 2013, NVIDIA GRID has supported GPU cards based on two generations of GPU hardware architecture:④GRID K1 and K2 GPU cards based on the NVIDIA Kepler™ architecture④Tesla M6, M10, and M60 GPU cards based on the NVIDIA Maxwell™ architecture NVIDIA GRID has seen considerable software innovation to continue to drive the best performance and density on the market.Software and Hardware Used in the TestsThe tests described in this guide are based on the following combinations of software and hardware:④VMware Horizon running the first-generation NVIDIA GRID K2 GPU④VMware Horizon and NVIDIA GRID Virtual Workstation software running on thesecond-generation Tesla M60 GPUAs shown in Table 1, using the latest generation provides better performance and scalability, and the ability to take advantage of new features and functionality of the software.Table 1 Comparison of GRID K2 and Tesla M60Hardware Encoding with NVENC and VMware Blast ExtremeNVIDIA and VMware have been working together for several years to improve the virtualized computing user experience and enable a completely new class of virtual use cases. NVIDIA was the first vendor to enable hardware-accelerated graphics rendering in VMware Horizon View. NVIDIA then enabled the first virtualized graphics acceleration in VMware Horizon View with GRID.The VMware Blast Extreme protocol, which was released in VMware Horizon 7, enables NVIDIA GRID to offload the H.264 processing from the CPU to the GPU. This offloading frees resources for use by internal applications, increasing user density and application responsiveness. The H.264 codec lowers the demand on network infrastructure, enabling organizations to reach more users over greater network lengths. VMware offers multiple protocols that are designed for different workloads. The choice of protocol may impact performance, density, image quality, and other factors. Therefore, you must select the best protocol for the needs of your organization. For more information about Horizon with Blast Extreme, refer to Blast Extreme Display Protocol in Horizon 7.This section describes the tests performed and the method of testing used to determine sizing and server loads.THE PERFORMANCE ENGINEERING LABThe mandate of the NVIDIA GRID Performance Engineering Team is to measure and validate the performance and scalability delivered by the NVIDIA GRID platform, namely GRID software running on Tesla GPU’s, on all enter prise virtualization platforms. It is the goal of the Performance Engineering Team to provide proven testing that gives NVIDIA’s customers the ability to deliver a successful deployment.The NVIDIA Performance Engineering Lab holds a wide variety of different OEM servers, with varying CPU specifications, storage options, client devices, and network configurations. This lab of enterprise virtualization technology provides the Performance Engineering team with the capacity needed to run a wide variety of tests ranging from standard benchmarks to reproducing customer scenarios on a wide range of hardware.None of this work is possible without the cooperation of ISVs, OEMs, vendors, partners, and their user communities to determine the best methods of benchmarking in ways that are both accurate and reproducible. These methods will ultimately assist mutual customers of NVIDIA and other vendors and OEMs to build and test their own successful deployments. In this way, the Performance Engineering Team works closely with its counterparts in the enterprise virtualization community.RECOMMENDED REVIT PHYSICAL SYSTEM CONFIGURATIONPhysical system requirements for Autodesk Revit 2016 are listed on the Revit product page. Testing focuses on recommended specifications when feasible. The goal is to test both performance and scalability, maintaining the flexibility and manageability advantages of virtualization without sacrificing the performance end users expect from NVIDIA powered graphics.It has been well documented that storage performance is key to providing high performance graphics workloads, especially with many users and ever-growing file or model sizes. In the NVIDIA Performance Engineering Lab, a 10G iSCSI-connected all flash SAN from Dell EMC XtremeIO was used. At no time in these tests were IOPS an issue, but note that as you scale to multiple servers hosting many guests, IOPS needs to be monitored.TYPICAL REVIT WORKSTATION BUILDSAutodesk delivers a recommended hardware specification to help choose a physical workstation. These recommendations provide a good starting point from which to start architecting your virtual desktops. Your own tests with your own models will determine if these recommendations meet your specific needs.Table 2 lists server configuration used for the benchmark tests described in this guide. This configuration is based on testing results from the RFO benchmarks, input from VMware, and feedback from mutual customers.Table 2 Server Configuration for Benchmark Testing of Revit 2016AUTODESK REVIT BENCHMARK METRICS (RFO) Autodesk provides a tool called AUBench which, when combined with the scripts provided by the Revit Forums community, creates a benchmark called RFO. RFO interacts with the application and an accompanying model to run several tests, then checks the journal for time stamps, and reports the results. The benchmark is available from the RFOBenchmark thread on the Revit Forum.These tests are designed to represent user activities and are broken down as follows: ④Model Creation and View and Export of Benchmarks●Opening and Loading the Custom Template●Creating the Floors Levels and Grids●Creating a Group of Walls and Doors●Modifying the Group by Adding a Curtain Wall●Creating the Exterior Curtain Wall●Creating the Sections●Changing the Curtain Wall Panel Type●Exporting all Views as PNGs●Exporting Some Views as DWGs④Render Benchmark●Render④GPU Benchmark1 with Hardware Acceleration●Refresh Hidden Line View ×12 - with Hardware Acceleration●Refresh Consistent Colors View ×12 - with Hardware Acceleration●Refresh Realistic View ×12 - with Hardware Acceleration●Rotate View ×1 - with Hardware Acceleration④GPU Benchmark1 Without Hardware Acceleration●Refresh Hidden Line View ×12 - Without Hardware Acceleration●Refresh Consistent Colors View ×12 - Without Hardware Acceleration●Refresh Realistic View ×12 - Without Hardware Acceleration●Rotate View ×1 - Without Hardware AccelerationTEST WORKLOADSTo ensure you will be able to reproduce the results described in “Test Results,” onpage 11, the Revit Forums RFO Benchmark workload was deliberately chosen and simultaneous tests were executed. As a result, all virtual desktops in the test perform the same activities at the same time. A “peak workload” should be unrepresentative of real user interaction but shows the number of users per host when the load on the shared resources is highest and, therefore, represents the most extreme case of user demand.If you plan to run these tests, consider these aspects of the test workloads:④Sample workload. RFO provides their workload, which is a set of models, fortesting with.④Scripting. As RFO is historically designed for single physical workstation testing,there is no built-in automation for multi-desktop scalability testing.④Think time. Pausing between tests simulates human behavior.④Staggered start. Adding a delay to the beginning of each test offsets the impact ofrunning the tests in unison, again, simulating human behavior.④Scalability. In general, the tests are run with 1 virtual desktop, then 8 virtualdesktops, and finally 16 virtual desktops. These test runs get a baseline of results and accompanying logs (CPU, GPU, RAM, networking, storage IOPS, and so forth.).1 For the hardware acceleration comparison only.HOW THE TESTS WERE RUN1.Virtual machines were created with a standard configuration to determine thethreshold of acceptable performance.2.The RFO benchmark was run with an individual VM on each GRID K2 and TeslaM60 system to determine the peak performance when there was no resourcecontention.3.To determine acceptable performance at scale, a 25% increase in the test timerequired for the total of the tests below was added to the value obtained in theprevious step.4.The threshold of performance in virtual environment testing was done successfullyacross multiple applications.5.After the performance threshold for Revit 2016 from the single VM tests wasdetermined, it was used to indicate peak user density for all systems in this guide.TEST LIMITATIONSBy design, this type of peak performance testing leads to conservative estimates of scalability. Automated scalability testing is typically more aggressive than a typical user workflow. In most cases, rendering requests are unlikely to be executed by 10 users simultaneously or even to the degree that was replicated in multiple test iterations. Therefore, the results from these automated scalability tests can be considered a worst-case scenario. They indicate likely minimums for rare conditions to serve as safe guidelines. In most cases, a host should be able to support more than the number of VMs indicated by the test results.The scalability in typical or even heavily loaded data centers is likely to be higher than the test results suggest. The degree to which higher scalability would be achieved depends on the typical day-to-day activities of users, such as the amount of time spent in meetings, the length of lunch breaks or other breaks, the frequency of multitasking, and so forth.The test results show execution times for performing various operations under varying conditions and compare CPU utilization against GPU utilization. The recommendations for the number of users per system suggested by these results is a balance between the need for greatest scalability and the performance expectations of users. Note that your users, your data, and your hardware will impact these results and you may decide that a different level of performance or scalability is required to meet your individual business needs.TEST THRESHOLD TIMESThe RFO Benchmark does not currently exercise some of Revit’s newest GPU capabilities and was built to push the limits of dedicated hardware as opposed to the shared resources of VDI. Therefore, the decision was made to stop testing when the test times had increased to 125% of values measured on a single virtual workstation.Table 3 shows the test threshold times for the NVIDIA GRID K2 and Tesla M60 cards. Table 3 Test Threshold TimesGRID K2 TEST EXECUTION TIMESTable 4 shows test execution times for the GRID K2 system with 8, 12, and 16 VMs. Note that at the maximum possible number of users (16 by design), the total test time (248.90) is still less than the threshold value of 261.84. Therefore, 16 users can comfortably reside on the same GRID K2 server.Table 4 GRID K2 Test Execution TimesTESLA M60 WITH NVENC TEST EXECUTION TIMES Table 5shows the test execution times when the Tesla M60 is accessed through the VMware Blast Extreme protocol. Note that the number of users per host is increased to 28.This improvement is attributable to the improved Tesla M60 GPU and the use by Blast Extreme of the NVIDIA Video Encoder (NVENC) technology. The use of Blast Extreme allows Horizon to offload encoding of the H.264 video stream from the CPU to dedicated encoder engines on the Tesla GPUs, freeing up this much-needed resource for general computing purposes.The video codec is a very important piece in delivering a remarkable user experience because it impacts many factors, such as like latency, bandwidth, frames per second (FPS), and other factors. Using H.264 as the primary video codec also allows VMware to use millions of H.264 enabled access devices to offload the encode-decode process from the CPU to dedicated H.264 engines on NVIDIA GPUs.Table 5 Tesla M60 with NVENC Test Execution TimesTEST EXECUTION TIMES WITH AND WITHOUT HARDWARE ACCELERATIONThe RFO Benchmark also provides results for testing with only CPU, and not using GPU at all. For these particular tests, the GPU is ignored by the software if present, and only CPU is used to graphics processing. This test has been included in the RFO benchmark for illustrative purposes, and we present the results here for the same reasons. It is, in our opinion, highly unlikely that anyone would seriously consider using a graphics intensive application such as Revit without the benefit of a GPU. In the event that someone does, the following tables illustrate the potential pitfall of doing so.Table 6 and Figure 2 show the value of using a GPU in the VM with Revit 2016. CPU only response times (“without hardware acceleration”) are increased by a factor of ten or more.For all cases, CPU-only tests (without hardware acceleration) for a single VM take more time than 16- and 24-VM tests with a GPU (with hardware acceleration).2 Exceeds the threshold of 261.84.Table 6 Test Execution Times with and Without Hardware Acceleration (with GPU)Figure 2 Test Execution Times with and Without Hardware AccelerationCPU UTILIZATION AGAINST GPU UTILIZATIONFigure 3 shows for the M60-1Q GPU profile that the CPU becomes a limiting factor long before the GPU resources are exhausted.Revit requires significant CPU resources so investing in more cores can yield greater performance and scalability. For medium-to-large models, M60-1Q performance will be better for a real-use scenario than a M60-0Q profile, which doesn’t provide enough frame buffer for satisfactory performance for Revit workloads. However, your results will vary. Therefore, you must test with your own models to ensure the most accurate results.Figure 3 CPU and M60-1Q GPU UtilizationThe test results show that with NVIDIA GRID K2 GPUs, one reference server can support up to 16 users without exceeding the 125% threshold set by our testing team. With NVIDIA Tesla M60 GPU accelerators with VMware Horizon and Blast Extreme, 28 users per server is achievable.As testing has shown, Autodesk Revit is CPU intensive because it uses database software to manage the elements of a drawing. Therefore, the more complex the model, the more CPU intensive the software will become. When calculating scalability, be aware that the CPU will become the bottleneck before the GPU.In practice, consolidating similar loads onto servers containing GPUs is preferable to running mixed workloads. Plan for these systems to run Revit or other GPU intensive loads, leaving servers that lack GPUs for loads that are not GPU intensive.NoticeALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.HDMIHDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of HDMI Licensing LLC.OpenCLOpenCL is a trademark of Apple Inc. used under license to the Khronos Group Inc.TrademarksNVIDIA and the NVIDIA logo are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.Copyright© 2017 NVIDIA Corporation. All rights reserved.BPG-08489-001。

Visio操作手册旨在帮助用户更好地掌握Visio的基本操作和应用，以下是一些Visio操作的基础步骤：
1. 创建形状：在Visio中，您可以使用各种形状工具创建各种形状，包括矩形、圆形、椭圆形、三角形等。

选择适当的形状工具，在画布上单击并拖动鼠标即可创建形状。

2. 移动形状：选择要移动的形状，按住鼠标左键并拖动鼠标即可移动形状。

如果要同时移动多个形状，请按住Ctrl键并单击要移动的形状。

3. 调整形状大小：选择要调整大小的形状，然后拖动其边缘或角落即可调整其大小。

如果要同时调整多个形状的大小，请按住Shift 键并单击要调整的形状。

4. 连接形状：在Visio中，您可以将形状连接在一起以创建更复杂的图表。

选择要连接的形状，然后单击“连接”工具将其连接在一起。

您还可以使用线条工具创建更复杂的连接。

5. 添加文本：选择要添加文本的形状，然后单击“文本”工具即可添加文本。

您还可以双击形状以打开文本编辑器。

6. 应用样式：Visio提供了各种样式和主题，您可以使用它们来美化您的图表。

选择要应用样式的形状或文本，然后单击“格式”菜单中的“样式”选项即可选择适当的样式。

7. 保存和导出图表：完成图表后，您需要将其保存和导出。

单击“文件”菜单中的“保存”选项即可保存图表。

您还可以将图表导出为各种格式，例如JPEG、PNG、PDF等。

以上是Visio操作手册的基础内容，希望对您有所帮助。

如有任何进一步的问题，请随时提问。