FastObjects.NET Migration Guide. Release 12.0

Transcription

1 Release 12.0

2 : Release 12.0 FastObjects Release 12.0 Copyright Versant Software LLC and Copyright Actian Corporation. All rights reserved. The software described in this document is subject to change without notice. This document does not represent a commitment on the part of Versant or Actian. The software is furnished under a license agreement or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or for any purpose without the express written permission of Actian. Versant, Versant Object Database and FastObjects are either registered trademarks or trademarks of Versant Software LLC in the United States and/or other countries. Java and all Java-based marks are trademarks or registered trademarks of Oracle Corporation in the United States and other countries. Eclipse and Built on Eclipse are trademarks of Eclipse Foundation, Inc. Microsoft, Windows, Visual C#, Visual Basic, Visual J#, and ActiveX are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other products are a registered trademark or trademark of their respective company in the United States and/or other countries V9-6

3 Table of Contents Contact Information for Actian... v About this Guide... vii 1. What's New in FastObjects FastObjects Application and Server 64-bit support FastObjects Server Scalability Enhancement FastObjects Server Performance optimization for.net (and Java) applications FastObjects Server Unlimited parallel connections Server usability Operation Monitoring Client-side scalability optimization Recovery file improvements Improved performance for queries using the index cache Improved performance for reindex, reorg and check Windows Native Authentication Bit support for Solaris Transactional removal of deleted indexes during update New Features in FastObjects 12 since FastObjects Bit Support for Linux Configuration of the System File Cache Size Performance improvement for reading objects greater than 1024 bytes Improved, configurable progress information during long queries Query debug output can be configured during runtime All FastObjects runtime DLLs now have a predefined base address Additional behavior for incremental sequences Faster query execution for complex queries Better performance when extracting embedded class sets or basic type sets Memory optimization for better performance Performance optimization in C/S communication Improved memory allocation for very large query results Better query estimation for conditions on indexed members Large transaction performance optimization FastObjects Connect Cascading Delete Compatibility Issues Supported Platforms Supported Visual Studio.NET Frameworks Supported.NET Languages API and Database Compatibility Client/Server Compatibility New default for maximum file size iii

4 3.7. FastObjects Storage Clustering enabled by default Best scalability enabled for FastObjects Server by default FastObjects Connect FastObjects Encryption iv

5 Contact Information for Actian You can obtain the latest information about Actian products by contacting either of our main office locations, visiting our web sites, or sending us an . Actian Office Locations Actian Corporation is headquartered in Redwood City, California. Versant GmbH is responsible for European operations and has headquarters in Hamburg, Germany. Actian Corporate Headquarters 500 Arguello Street, Suite 200 Redwood City, CA USA [TEL] [FAX] Versant GmbH Halenreie 42 D Hamburg Germany +49 (0) [TEL] +49 (0) [FAX] Actian Web Site For the latest corporate and product news, visit the Actian web site at Actian Versant Products For inquiries about Versant products and services, contact: info@versant.com For help in using Versant products, contact Technical Support at: versant_support@actian.com The Actian Customer Portal provides all the essential information and valuable resources needed by developers using Versant Object Database or Versant FastObjects. Visit the Actian Customer Portal at support.actian.com v

6 Please send feedback regarding this guide to: vi

7 About this Guide This guide presents a quick overview of new features and funtionality in FastObjects.NET 12 and describes changes and additions to be aware of when moving an existing application from FastObjects.NET Release 10 to FastObjects.NET Release 12. vii

8 viii

9 Chapter 1. What's New in FastObjects FastObjects Application and Server 64-bit support FastObjects.NET 12 applications (built with Visual Studio bit) can run in 64-bit mode. A 64-bit version of the FastObjects Server is also now supplied. New FastObjects data types for representing 8-byte integral types are introduced FastObjects Server Scalability Enhancement Parallel access to the same object has been improved FastObjects Server Performance optimization for.net (and Java) applications Transaction commit/rollback is now much faster FastObjects Server Unlimited parallel connections In previous versions of FastObjects, the maximum number of connections was limited to With FastObjects 11 the number of connections is limited only by the required virtual memory of the threads created for that connection Server usability Output to console, Server view, and file is configurable at runtime. Server view is available in the FastObjects Administrator. 1

10 Operation Monitoring Client-side scalability optimization 1.6. Operation Monitoring Client-side scalability optimization Performance improvement for applications using operation monitoring with many OperationHandler instances Recovery file improvements Changes to the FastObjects database are stored in a recovery file until the changes have been fully integrated into the database files. In previous versions the changes are written to the recovery file with a fixed chunk size of four kilo-bytes (4 KB). With FastObjects 12.0, the default chunk size is now 256 KB and is configurable in the FastObjects configuration file. [] recoverychunksize = 256 In order to find the optimum setting for a specific disk system, a benchmark can be run from the command line Fastobjects Server or ptserver -testrecovery ptserver64 -testrecovery This command prints the average time for various chunk sizes. Current disk systems perform much better than previous systems when large data-write requests. Especially RAID systems and SSD (Solid State Disk) systems will benefit from a larger chunk size. Depending on the underlying disk system the performance gain can be up to factor of five for the default recovery options Improved performance for queries using the index cache FastObjects uses a cache for index nodes for each index. In previous versions theses caches have often been invalidated when used for transactions which modified index nodes. In FastObjects 12.0 joint index caches are used to increase the effectiveness of the cache. Queries, especially, will 2

11 Improved performance for reindex, reorg and check benefit from the new cache implementation. The number of cached index nodes for each index can be configured individually. The default for each user defined index (indexcachecount) is 500 index nodes. The default for each all set/extent index (extentcachecount) is 50 index nodes. The default for the PtObjectAllSet index (the index for all persistent objects) is index nodes. In addition the number of cached index nodes for user indexes and the PtObject extent index has been increased. [] indexcachecount=500 # default was 100 index nodes in previous releases extentcachecount=50 # same default as in previous releases [databases\mybase\indexes\ptobject] # Settings in this section override settings made in the global section for the data\ base mybase extentcachecount=10000 # number of index nodes cached for the PtObjectAllSet index The total amount of memory used for all index caches is restricted with the configuration entry maxindexcachesizemb. The default is 10 MB. [] maxindexcachesizemb = 10 Please refer to the FastObjects Configuration Guide for more details. Additionly, the concurrent access to the index cache has been optimized for higher performance and increased scalability Improved performance for reindex, reorg and check The performance for the database administration reindex, reorg and check commands has been improved. Database files that must be scanned sequentially during these operations are now opened in sequential scan mode and are using an internal buffer to read ahead in the file. This allows a much better throughput when scanning the entire database file. The read ahead buffer size can be configured in the FastObjects configuration file: 3

12 Windows Native Authentication [] sequentialfilecachechunksizekb = 512 The value is in KB. The default is 256. This optimization is used for the database check command only if the database is opened in the new exclusive open mode. The FastObjects Database Administration Utility ptadmin is using this new open mode by default. In order to perform a database check on a database that is opened by other FastObjects client applications the check needs the new -concurrent option: ptadmin -check -concurrent In addition, the new joint index cache speeds up the reindex and reorg operations and the maximum size used for the index cache (maxindexcachesizemb) should be increased accordingly. As a rule-of-thumb, half of this memory should be configured for the PtObject AllSet/extent index Windows Native Authentication FastObjects now provides a Windows Security Support Provider Interface (SSPI) Negotiate package implementation for Kerberos and NTLM (Windows NT LAN Manager) authentication. Refer to the FastObjects Server User's Guide, chapter Connecting Clients to the FastObjects Server for more information Bit support for Solaris The FastObjects Server is available for 64-bit Solaris SPARC platforms Transactional removal of deleted indexes during update When a database is updated with a dictionary where indexes are removed from the schema, then these indexes are removed from the database as well. However, in previous releases the removal of indexes was not transactional and aborting the update process could leave the database in an inconsistent state. Now the removal of an index is done inside of an internal transaction. The maximum size of the internal transaction is determined via the setting admincachesize. 4

13 Transactional removal of deleted indexes during update [] admincachesize=16384 # default is KB 5

14 6

15 Chapter 2. New Features in FastObjects 12 since FastObjects Bit Support for Linux The FastObjects Server is available in 64 bit mode for Linux platforms Configuration of the System File Cache Size Symptom The read and write access to the FastObjects databases files benefit from the system file cache of the operating system. On Windows 64-Bit operating systems the working set of the Windows System File Cache (WSFC) is unlimited by default. That means that the working set of the WSFC can grow until all physical memory of the machine is exhausted. If this happens then all other applications start to swap. Microsoft provides the tool "Microsoft Windows Dynamic Cache Service" that runs as a service and keeps the working set of the WSFC on a configured level. This tool denies the installation on Windows Server 2008 R2, because a more sophisticated algorithm has been implemented for the WSFC on Windows Server 2008 R2. However, in some scenarios with extensive write access on Windows Server 2008 R2 the working set of the WSFC still keeps growing and causes other applications to swap. Now, the FastObjects Server can be configured to set the minimum and maximum size of the system file cache working set for the machine at startup. If both of the following configuration entries are present in the ptserver.cfg, then the FastObjects Server tries to configure the minimum and the maximum size of the system file cache at startup. [servers\ptserver] # Sets minimum to 150 MB. windowsminsystemfilecachesizemb = 150 # Sets maximum to 80% of physical memory. windowsmaxsystemfilecachesizemb = 80 The value for windowsminsystemfilecachesizemb determines the minimum of the working set of the system file cache in MB. If the value is negative, the minimum is set to disabled. The FastObjects Server 32-Bit cannot set a value larger than 4095 and will use 4095 for larger values. The minimum has to be at least 100 MB. If the value is smaller then 100 MB is used. 7

16 Performance improvement for reading objects greater than 1024 bytes The value for windowsmaxsystemfilecachesizemb determines the maximum of the working set of the system file cache. A value of determines the percentage of the physical memory that shall be used as the maximum. A values greater than 100 determines the maximum in MB. If the value is negative then the maximum is set to disabled. The FastObjects Server 32-Bit cannot set a value larger than 4095 and will use 4095 for larger values. The maximum has to be at least 100 MB larger than the minimum. Otherwise it will be set to the minimum MB. The actual calculated values for the system file cache size are reported to the Windows Application Eventlog. Notes The FastObjects Server needs administrative rights (as for the local system account) in order to set the system file cache size This setting will affect the performance of all applications on that machine The Windows API SetSystemFileCacheSize() is not available on all Windows platforms The FastObjects Server will startup regardless of any errors during the configuration of the system file cache size Errors are reported to the Windows Application Eventlog If the FastObjects Server 32-Bit is running on a Windows 64-Bit platform, then values higher than 4095 MB are reverted to 4095 MB due to 32-Bit API restrictions 2.3. Performance improvement for reading objects greater than 1024 bytes Previously, when an object larger than 1024 bytes was read from the database file, several read requests were issued to the disk in order to read the object record. Now, after reading the first cluster with the record header the rest of the object is read in one read request. 8

17 Improved, configurable progress information during long queries 2.4. Improved, configurable progress information during long queries A new configuration setting pendingmaxobjects has been introduced which can be set in the global section or per database to trigger a pending notification after a maxium number of executed objects has been reached during query loops. The default is Query debug output can be configured during runtime The FastObjects Server console can provide detailed information about query tasks, used indexes and query execution times. ptserver.cfg [debug] query=5 # default is 0 In FastObjects 12, this setting is evaluated every time the configuration file is read by the FastObjects Server, for example, when opening a database. (Reading the configuration file can also be forced by setting the verbose mode with the command line tool ptsu.) The FastObjects Server no longer needs to be restarted to evaluate this configuration setting. Enabling the query debug output does reduce the performance of the FastObjects Server and should be used in production environments only as needed All FastObjects runtime DLLs now have a predefined base address For Windows platforms, all FastObjects Runtime DLLs have predefined base addresses allowing the 32-Bit FastObjects Server to allocate more continuous memory. 9

18 Additional behavior for incremental sequences 2.7. Additional behavior for incremental sequences A new behavior can be configured for incremental sequences. Integral data types can be registered for providing an incremental sequence number on creation without a gap (autovalue=incrementoncreate). [] useexistingsequentialid = true This configuration provides an incremental sequence number only if that member is zero (default value for integral types). Otherwise the existing value for this member is used for storing the object Faster query execution for complex queries A query in FastObjects is executed in several query tasks. Depending on the result of a task other tasks do not need to be executed. The query engine has been improved to better decide to exclude dependent query tasks from execution. This can speed up complex queries and also fixes situations where the sort criteria has not been taken into account Better performance when extracting embedded class sets or basic type sets The calculation of the buffer size needed when extracting the data from an object into a buffer has been improved. This applies to the estimated size for sets of embedded classes with fixed size and for sets of basic types. The result is better performance owing to fewer memory allocations and less memory fragmentation Memory optimization for better performance A number of improvements has been made to memory allocation when using large collections. Faster memory grow algorithm for all sets The internal representation for sets uses a contiguous chunk of memory. If more memory is needed for adding an element then the memory chunk is 10

19 Performance optimization in C/S communication expanded to a new size. This algorithm was optimized for a small memory footprint. However, for very large sets this algorithm is slow and can lead to memory fragmentation. Now this algorithm is optimized for speed. This affects all sets used in persistent classes and internally in the FastObjects Runtime System and in the FastObjects Server. Less allocations for collection of client/server requests in client applications In C/S mode certain kind of calls (forgets, locks, forgets in batch transaction commit) are collected and sent to the FastObjects Server in one single C/S call. Now that collection starts with an expected num of 500 and will be shrinked to elements after the C/S call. The following configuration entries have been introduced for fine tuning. poet.cfg [] collectedserverrequestexpectednum=500 # default is 500 collectedserverrequestshrinkthresholdnum=10649 # default is Optimization for sequential queries and PtOnDemandSet queries in the FastObjects Server The initial size for the set that is used for collecting matching objects has been increased. In addition the optimized grow algorithm speeds up query execution Performance optimization in C/S communication When receiving a job (on the client or server side) FastObjects 12 now performs fewer memory allocations. This optimization results in faster communication between client and server Improved memory allocation for very large query results Previously, when receiving the result set for very large results (several million objects), many many memory allocations took place causing memory fragmentation. This allocation has been significantly improved with a corresponding increase in performance for large query results. 11

20 Better query estimation for conditions on indexed members Better query estimation for conditions on indexed members The FastObjects query optimizer estimation on indexed members has been improved. Query conditions that do not match objects are detected earlier detected leading to a more efficient query plan. This increases query execution performance Large transaction performance optimization The performance for committing transactions has been improved. All modifying operations benefit from this optimization. Large transactions benefit the most FastObjects Connect SQL views are now available in the ODBC catalog Cascading Delete Now deleting an object will also delete referenced objects that are marked as dependent with the DependAttribute. By default all references to objects and collections of references to objects are registered as non-dependent. For deleting objects without their dependent objects a transaction property can be set. scope.transactionproperties.deletedependent = false; 12

21 Chapter 3. Compatibility Issues This chapter provides a summary of compatibility issues you may encounter when moving from FastObjects.NET release 10 to Supported Platforms Windows The following Windows platforms are supported (both 32-bit and 64-bit editions): Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R Supported Visual Studio.NET Frameworks You can use Microsoft Visual Studio 2010 (SP1) with.net Framework 4.0 for application development. Earlier versions of Visual Studio and.net Framework are no longer supported Supported.NET Languages FastObjects.NET Release 12 supports C# and Visual Basic. Support for J# is discontinued API and Database Compatibility New data types for integral types representing 8-bytes have been introduced for 64-bit support. Existing dictionaries need to be converted before the new data types can be registered. New dictionaries that are created with FastObjects 12 have the new dictionary format that allows for the new data types. Before you register your schema with FastObjects 12 you should consider if your application needs 64-bit support. Depending on the required compatibility level additional settings are required for schema capturing. By default, the new datatypes for 8-byte integral types will be registered in existing dictionaries that are converted to FastObjects If you need to maintain the original 13

22 Client/Server Compatibility datatypes, in the Visual Studio Properties Window for the project, you must set the project property FO10_Compatibility to true Client/Server Compatibility As installed, FastObjects 10.0 clients cannot connect to FastObjects bit server. However, FastObjects bit can be configured to accept FastObjects 10.0 clients with the following entry in the server configuration file. [] usegeneratedserviceid=true Client performance may be slightly reduced New default for maximum file size The maximumfilesize property determines the maximum size for database eventlog files and incremental backup files. The previous default was The new default is [] maximumfilesize= FastObjects Storage Clustering enabled by default Databases can be configured to store all new objects in a transaction to the same location in the database file. This is beneficial for storing, accessing, and deleting object networks. The database can grow faster when using this configuration if contiguous space for the new objects cannot be reclaimed from deleted objects and the database file needs to grow. Starting with FastObjects 12.0 it is enabled by default. FastObjects Storage Clustering can be disabled for all databases in the configuration file. [] storageclusteringpattern=none 14

23 Best scalability enabled for FastObjects Server by default 3.8. Best scalability enabled for FastObjects Server by default The FastObjects Server can be configured for best scalability. This can be done by setting the concurrencylevel property in the configuration file of the FastObjects Server to the value 12. In FastObjects 12.0 this setting is enabled by default. You can configure the previously used concurrency level in the configuration file of the FastObjects Server (ptserver.cfg). [servers\ptserver] concurrencylevel=9 # default is FastObjects Connect Simba Engine replaces the previously used Simba Engine Fastobjects Connect supports ODBC 32-bit only FastObjects Encryption The OpenSSL version used is now 1.0.1g (the previously used version was 0.9.7b). In addition, the FastObjects library filenames are now named depending on the compiler and run-time (32- or 64-bit) mode. For example, the SSLeay library for Windows for VisualStudio 2010, 64-bit is SSLeay100x64.dll. Refer to the FastObjects Application Deployment Guide for more information. 15

24 16