Abstract: A serverless query processing system receives a query and determines whether the query is a recurring query or a non-recurring query. The system may predict, in response to determining that the query is the recurring query, a peak resource requirement during an execution of the query. The system may compute, in response to determining that the query is the non-recurring query, a tight resource requirement corresponding to an amount of resources that satisfy a performance requirement over the execution of the query, where the tight resource requirement is less than the peak resource requirement. The system allocates resources to the query based on an applicable one of the peak resource requirement or the tight resource requirement. The system then starts the execution of the query using the resources.

Abstract: A serverless query processing system receives a query and determines whether the query is a recurring query or a non-recurring query. The system may predict, in response to determining that the query is the recurring query, a peak resource requirement during an execution of the query. The system may compute, in response to determining that the query is the non-recurring query, a tight resource requirement corresponding to an amount of resources that satisfy a performance requirement over the execution of the query, where the tight resource requirement is less than the peak resource requirement. The system allocates resources to the query based on an applicable one of the peak resource requirement or the tight resource requirement. The system then starts the execution of the query using the resources.

Abstract: A serverless query processing system receives a query and determines whether the query is a recurring query or a non-recurring query. The system may predict, in response to determining that the query is the recurring query, a peak resource requirement during an execution of the query. The system may compute, in response to determining that the query is the non-recurring query, a tight resource requirement corresponding to an amount of resources that satisfy a performance requirement over the execution of the query, where the tight resource requirement is less than the peak resource requirement. The system allocates resources to the query based on an applicable one of the peak resource requirement or the tight resource requirement. The system then starts the execution of the query using the resources.

Abstract: Techniques are described herein that are capable of selecting checkpoints of a database job. For instance, at compile time, temporal indicators associated with the query plans of the database job are determined. Each temporal indicator indicates first and second subsets of stages of the respective query plan. Values of attributes of each stage in at least each first subset are predicted using a machine learning technique. At the compile time, candidate stage(s) for each query plan are identified based on the respective candidate stage being a child of stage(s) in the corresponding second subset or not being a child of another stage in the respective query plan. The candidate stage(s) for each query plan are selectively chosen as respective checkpoint(s) based on whether the values of the attributes of each stage in at least the first subset of the stages of the respective query plan satisfy one or more criteria.

Abstract: Techniques are described herein that are capable of selecting checkpoints of a database job. For instance, at compile time, temporal indicators associated with the query plans of the database job are determined. Each temporal indicator indicates first and second subsets of stages of the respective query plan. Values of attributes of each stage in at least each first subset are predicted using a machine learning technique. At the compile time, candidate stage(s) for each query plan are identified based on the respective candidate stage being a child of stage(s) in the corresponding second subset or not being a child of another stage in the respective query plan. The candidate stage(s) for each query plan are selectively chosen as respective checkpoint(s) based on whether the values of the attributes of each stage in at least the first subset of the stages of the respective query plan satisfy one or more criteria.

Abstract: In most of today's computer aided design (CAD), there are many definitive relationship between how components used in a CAD design relate to other components and feature in the same design. These relationships include sizing (a component is sized based upon another component), placement and orientation (a component is position and orientated based upon another component or feature). In addition, certain components can only be used with other specific components within the same design. Various attributes are placed on the CAD components and features that relate to each other that will be used to automatically size, place and orientate components, as well as make sure the component is valid to be used within the design intent. This saves designers considerable amount of design time as well as ensuring accurate component to component relationship as used in their design.

Abstract: Described herein is a system and method for detecting and reusing overlapping computations. Overlapping subgraphs of the query are determined using a normalized signature for a particular subgraph that identifies a particular subgraph across recurring instances of data. A normalized signature for each overlapping subgraph for the determined overlapping subgraphs of the query is provided. For each overlapping subgraph determined to be materialized: whether or not the particular subgraph has been materialized is determined using a precise signature corresponding to a normalized signature of the particular overlapping subgraph. The precise signature identifies a particular subgraph corresponding to the normalized signature within a particular recurring instance of data. When the particular subgraph has not been materialized, the subgraph is materialized and used to respond to the query. When the particular subgraph has been materialized, the materialized subgraph is used to respond to the query.

Abstract: A serverless query processing system receives a query and determines whether the query is a recurring query or a non-recurring query. The system may predict, in response to determining that the query is the recurring query, a peak resource requirement during an execution of the query. The system may compute, in response to determining that the query is the non-recurring query, a tight resource requirement corresponding to an amount of resources that satisfy a performance requirement over the execution of the query, where the tight resource requirement is less than the peak resource requirement. The system allocates resources to the query based on an applicable one of the peak resource requirement or the tight resource requirement. The system then starts the execution of the query using the resources.

Abstract: Disclosed is a parametric feature-based 3D CAD system that allows multiple users to simultaneously edit a parametric feature-based 3D CAD model consisting of 3D parts and assemblies of those parts (3D Model). Several CAD users, each using their own computer, phone, or tablet, can edit the same 3D Model at the same time. Editing may be separate and simultaneous—there is no need for users to worry about locking, checking out, or otherwise restricting each other's access to 3D Models. As a result, users see each other's changes occur in real-time, and may also identify what aspects other users are actively modifying through visible Collaboration Cues.

Abstract: Described herein is a system and method for detecting and reusing overlapping computations. Overlapping subgraphs of the query are determined using a normalized signature for a particular subgraph that identifies a particular subgraph across recurring instances of data. A normalized signature for each overlapping subgraph for the determined overlapping subgraphs of the query is provided. For each overlapping subgraph determined to be materialized: whether or not the particular subgraph has been materialized is determined using a precise signature corresponding to a normalized signature of the particular overlapping subgraph. The precise signature identifies a particular subgraph corresponding to the normalized signature within a particular recurring instance of data. When the particular subgraph has not been materialized, the subgraph is materialized and used to respond to the query. When the particular subgraph has been materialized, the materialized subgraph is used to respond to the query.

Abstract: Disclosed is a parametric feature-based 3D CAD system that allows multiple users to simultaneously edit a parametric feature-based 3D CAD model consisting of 3D parts and assemblies of those parts (3D Model). Several CAD users, each using their own computer, phone, or tablet, can edit the same 3D Model at the same time. Editing may be separate and simultaneous—there is no need for users to worry about locking, checking out, or otherwise restricting each other's access to 3D Models. As a result, users see each other's changes occur in real-time, and may also identify what aspects other users are actively modifying through visible Collaboration Cues.

Abstract: A method is disclosed to model a part in the context of one or more assembly states. This method stores references of one or more states of one or more assemblies that a user wants to model a part against, and allows the user to reference surrounding parts from references of assembly states in one or more parametric features. Each reference of assembly with other necessary data is stored in a user object called a context. The assembly can be modified to move components as per desired motion while the part is modeled against one or more assembly states. Also provided is an interface to manage assembly states that are important for a part design for relating to other parts in the assembly. Such interface lets the user update one or more assembly states and associated features for each state at any time during design cycle.

Abstract: Many computer aided design (CAD) models include components that are supplied via third party vendors, also know as suppliers. These suppliers create CAD models of their components, place them in a library organized by logical categories, and then place the library in a cloud enable database infrastructure, which allows access to the supplier's library by other CAD users. As other users create new CAD designs, they will access specific supplier libraries in the cloud and add references to various supplier components within their own CAD design. All the references to any supplier components by any end user is stored in the cloud database infrastructure, allowing the suppliers to query who and how their components are being used in any end users CAD design.

Abstract: In most of today's computer aided design (CAD), there are many definitive relationship between how components used in a CAD design relate to other components and feature in the same design. These relationships include sizing (a component is sized based upon another component), placement and orientation (a component is position and orientated based upon another component or feature). In addition, certain components can only be used with other specific components within the same design. Various attributes are placed on the CAD components and features that relate to each other that will be used to automatically size, place and orientate components, as well as make sure the component is valid to be used within the design intent. This saves designers considerable amount of design time as well as ensuring accurate component to component relationship as used in their design.

Abstract: A method is disclosed to model a part in the context of one or more assembly states. This method stores references of one or more states of one or more assemblies that a user wants to model a part against, and allows the user to reference surrounding parts from references of assembly states in one or more parametric features. Each reference of assembly with other necessary data is stored in a user object called a context. The assembly can be modified to move components as per desired motion while the part is modeled against one or more assembly states. Also provided is an interface to manage assembly states that are important for a part design for relating to other parts in the assembly. Such interface lets the user update one or more assembly states and associated features for each state at any time during design cycle.

Abstract: Technologies are generally described to identify foreground motion detection in compressed video data. In some examples, a foreground motion detection module may determine transform-coefficient-magnitude sums and motion-vector-magnitude sums associated with block coding units (BCUs) in compressed video data without decompressing the video data. The foreground motion detection module may also determine a background mean and a background co-variance associated with the compressed video data. To determine whether the BCU(s) contain foreground motion, the foreground motion detection module may determine a statistic based on the transform-coefficient-magnitude sums, the motion-vector magnitude sums, the background mean, and the background co-variance and compare the statistic to a threshold.

Abstract: A replication method for use within CAD software ignores parametric requirements and instead searches 3D geometry of components mated to a replication candidate directly for geometric elements that are identical to those on which the candidate is constrained. The system counts the number of identical geometric elements to determine the number of candidate instances to replicate, and then constrains one instance to each element with constraints equivalent to the constraints applying to the original candidate.

Abstract: A hydrometallurgical process is provided for the recovery of tellurium as elemental tellurium powder from copper refinery anode slime containing high amount of lead. The process involves the removal of copper and lead from anode slime followed by the recovery of tellurium as elemental powders. An economical and environment friendly process is provided for producing tellurium from a high lead bearing anode slime as it involves only hydrometallurgical techniques and thereby avoids emission of any polluting gases and has an efficiency of 85 to 90%. The developed process of recovering tellurium as elemental powders from copper refinery anode slime is beneficial in the production of pure tellurium instead of tellurium compounds. It helps raise the profit margin of a non-ferrous metal industry dealing with extraction of copper from ores and treatment of anode slime for the recovery of other metal values.

Abstract: Technologies are generally described to identify foreground motion detection in compressed video data. In some examples, a foreground motion detection module may determine transform-coefficient-magnitude sums and motion-vector-magnitude sums associated with block coding units (BCUs) in compressed video data without decompressing the video data. The foreground motion detection module may also determine a background mean and a background co-variance associated with the compressed video data. To determine whether the BCU(s) contain foreground motion, the foreground motion detection module may determine a statistic based on the transform-coefficient-magnitude sums, the motion-vector magnitude sums, the background mean, and the background co-variance and compare the statistic to a threshold.

Abstract: Disclosed is a parametric feature-based 3D CAD system that allows multiple users to simultaneously edit a parametric feature-based 3D CAD model consisting of 3D parts and assemblies of those parts (3D Model). Several CAD users, each using their own computer, phone, or tablet, can edit the same 3D Model at the same time. Editing may be separate and simultaneous—there is no need for users to worry about locking, checking out, or otherwise restricting each other's access to 3D Models. As a result, users see each other's changes occur in real-time, and may also identify what aspects other users are actively modifying through visible Collaboration Cues.