Developer
  • Projects
  • Docs
  • Blog
  • Forum
  • Builds
  • BLENDER.ORG

    • Download

      Get the latest Blender, older versions, or experimental builds.

    • What's New

      Stay up-to-date with the new features in the latest Blender releases.

    LEARNING & RESOURCES

    • Blender Studio

      Access production assets and knowledge from the open movies.

    • Manual

      Documentation on the usage and features in Blender.

    DEVELOPMENT

    • Developers Blog

      Latest development updates, by Blender developers.

    • Documentation

      Guidelines, release notes and development docs.

    • Benchmark

      A platform to collect and share results of the Blender Benchmark.

    • Blender Conference

      The yearly event that brings the community together.

    DONATE

    • Development Fund

      Support core development with a monthly contribution.

    • One-time Donations

      Perform a single donation with more payment options available.

Logo
Explore
Products
Blender User Manual Developer Documentation
Blender Benchmark
Blender Studio Tools Flamenco Watchtower
Modules
Animation & Rigging Asset System Core Grease Pencil Modeling Nodes & Physics Pipeline & I/O Platforms & Builds Python API & Text Editor Sculpt, Paint & Texture Triaging User Interface VFX & Video
Rendering
Render & Cycles Viewport & EEVEE
Report a Bug Paste Code Help
Sign In
archive/phabricator
1
0
Fork 0
You've already forked phabricator
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
Files
321b7761488d3199a2d29494a92009e4c5862b9e
phabricator/resources/sql/patches/101.heraldruleapplied.sql

3 lines
68 B
MySQL
Raw Normal View History

Remove massive "rule applied" query Summary: Herald rules may be marked as "one-time". We track this by writing a row with <ruleID, phid> when we apply a rule. However, the current test for rule application involves loading every <ruleID, *> pair. We also always write this row even for rules which are not one-time, so if there are 100 rules, we'll load 1,000,000 rows after processing 10,000 objects. Instead, load only the <phid, *> pairs, which are guaranteed to be bounded to at most the number of rules. I'll follow up with a diff that causes us to write rows only for one-time rules, and deletes all historic rows which are not associated with one-time rules. Test Plan: Grepped for callsites to loadAllByContentTypeWithFullData(). Ran rules in test console. Reviewers: nh, btrahan, jungejason Reviewed By: nh CC: aran, epriestley Differential Revision: https://secure.phabricator.com/D1483
2012-01-24 19:03:30 -08:00
ALTER TABLE phabricator_herald.herald_ruleapplied
ADD KEY (phid);
Reference in New Issue Copy Permalink
Powered by Gitea Page: 34ms Template: 2ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API