• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zodb / relstorage
96%
master: 92%

Build:
Build:
LAST BUILD BRANCH: 4.1.1
DEFAULT BRANCH: master
Repo Added 10 Jun 2016 11:39AM UTC
Files 234
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH mysql-myisasm
branch: mysql-myisasm
CHANGE BRANCH
x
Reset
  • mysql-myisasm
  • 1.6
  • 1.6-no-zeo
  • 1.6.1
  • 1.6.2
  • 1.6.3
  • 2.0.0
  • 2.0.0b4
  • 2.0.0b5
  • 2.0.0b6
  • 2.0.0b7
  • 2.0.0b8
  • 2.0.0b9
  • 2.0.0rc1
  • 2.1.0
  • 2.1.1
  • 2.1a1
  • 2.1a2
  • 3.0.0
  • 3.0.1
  • 3.0a10
  • 3.0a11
  • 3.0a12
  • 3.0a13
  • 3.0a2
  • 3.0a3
  • 3.0a4
  • 3.0a5
  • 3.0a6
  • 3.0a7
  • 3.0a9
  • 3.0b1
  • 3.0b2
  • 3.0b3
  • 3.0rc1
  • 3.1.0
  • 3.1.1
  • 3.1.2
  • 3.2.0
  • 3.2.1
  • 3.5.0
  • 3.6
  • 4.0.0
  • 4.0.0a1
  • 4.1.0
  • 4.1.1
  • ZODB5-before-instance-optimization
  • afterCompletion
  • appveyor
  • appveyor38
  • argparse
  • better-cache-validation
  • better-lock-algorithm
  • better_store_conn_cleanup
  • bigger_MVCC_depth_by_default
  • blobhelper-never-none
  • boost1_83-gcc13
  • boost_1_75
  • btrees472
  • cache-file-temp-better
  • cache-read-opts
  • check-cache-for-readCurrent
  • ci-for-pr-20
  • cleanup-blob-tests
  • commit-lock-ex
  • configure-sqlite
  • conflict-res-from-cache
  • coveralls-ignore-oracle
  • cython-3rc2
  • default-postgres-version
  • faster-cache-validation
  • faster-conflict-loading
  • faster-pack
  • faster-pg-gevent
  • faster-vacuum
  • file-time-tid
  • find_packages
  • finer-lru
  • fix-135-16
  • fix-135-master
  • gcc13-py12-updates
  • generic-txncontrol
  • github-actions
  • issue125
  • issue159
  • issue166
  • issue169
  • issue173
  • issue175
  • issue178
  • issue181
  • issue186
  • issue188
  • issue201
  • issue206
  • issue210
  • issue211
  • issue212
  • issue212-mysql
  • issue213
  • issue216
  • issue218
  • issue220
  • issue222
  • issue224
  • issue227
  • issue228
  • issue232
  • issue239
  • issue241
  • issue242
  • issue246
  • issue247
  • issue249
  • issue264
  • issue266
  • issue270
  • issue280
  • issue281
  • issue281-pg
  • issue283
  • issue291
  • issue293
  • issue296
  • issue302
  • issue304
  • issue310
  • issue311
  • issue311-take2
  • issue317
  • issue325
  • issue329
  • issue339
  • issue340
  • issue342
  • issue344
  • issue376
  • issue381
  • issue389
  • issue401
  • issue403
  • issue407
  • issue409
  • issue411
  • issue421
  • issue424
  • issue425
  • issue438
  • issue446
  • issue454
  • issue460
  • issue464
  • issue468
  • issue474
  • issue511
  • issue78
  • issue9
  • issuo61
  • jim-test
  • jim-zodb5
  • legacy-zodb-removal
  • lint
  • llbtree-delta
  • loadBefore-optimization
  • log-improvements
  • mamico-1.6-travis
  • master
  • monkey-zodb-139
  • more-logging
  • more-merging
  • more-tests-16
  • mvcc-logging
  • mysql-connector
  • mysql-set-min-oid
  • mysql-tid-rounding
  • native-updated-pypy
  • new-protocol
  • no-close-conn-vote-conflict
  • none_bucket_on_load
  • old-pypy
  • oracle-fixes
  • pcache-correct-tids
  • pcache-missed-update
  • pers-cache
  • persistent-cache-efficiency
  • pg-row-batcher-arrays
  • pg_faster_lock_and_move
  • poll-old-cache
  • poller_no_if
  • postgresql-lockless-commit
  • prep-statements
  • prep30a9
  • py-updates
  • py312
  • py36
  • py39
  • reduce-cache-locking
  • refactor-dbs
  • refactor-save
  • refactor-simple-service
  • revert-lock-order
  • rst-files
  • simplify-max-stored
  • simplify-tracing
  • smaller-include
  • sqlite-gevent
  • sqlite-optimize
  • sqlite-stats
  • storage-is-not-threadsafe
  • transaction2.0
  • travis37
  • umysqldb
  • unify-oids
  • unreleased-updates
  • update-mysqlconnector
  • update-zodb
  • use-unsigned-tree
  • w-tinylru
  • w-tinylru-cffi
  • wheels-on-travis
  • zodb522-blobs
  • zodbconvert-improvements

pending completion
605

push

travis-ci

jamadden
Use InnoDB temp tables

And truncate them.

For most things this seems to speed up writes by around 10% or more due
to the way the temp tables are allocated.

Tested on both 5.5 and 5.7.

I think the dropping was an attempt to make the tables statement-level
replication compatible, but since they weren't transactianal I don't
think that worked. They were also variable sized so I don't think there
were any speed benefits. It also didn't implicitly end the transaction,
but that's not a concern where this is called.

Here's a complete set of benchmarks against 5.7, comparing zodbshootout
with -c2 and -c6, -n 1000 and '-n 100 -s 256 --test-reps 200'. This
compares 2.0.0 with current master and this change, in that order.

** c=2,s=256 **                2.0.0   master   InnoDB
"Transaction",               mysql_hf
"Add 100 Objects",               8883     9199    10157
"Update 100 Objects",            9380     9169    10318

** c=6,s=256 **                 2.0.0    master   InnoDB
"Transaction",               mysql_hf
"Add 100 Objects",               ----     14913   15524
"Update 100 Objects",            ----     14914   15077

** c=6,s=128 **                 2.0.0    master   InnoDB
"Transaction",                mysql_hf
"Add 1000 Objects",              29815    31704    38506
"Update 1000 Objects",           28978    29030    29137

In all cases, InnoDB temp tables outperform, in some cases
substantially.

An earlier set of benchmarks taken against 5.5 (but prior to a rebase on
master, so not easily replicated). The absolute value difference in
numbers versus above is that these were taken with Py 3.4 while above
was py 2.7.

zodbshootout -c 2 shootout.conf -n 100 --test-reps 200 -r 1 -s 256

Before

** concurrency=2 **
"Transaction",               mysql_hf
"Add 100 Objects",               6493
"Update 100 Objects",            9636
"Read 100 Warm Objects",         9797
"Read 100 Cold Objects",         9336
"Read 100 Hot Objects",         37407
"Read 100... (continued)

6 of 6 new or added lines in 1 file covered. (100.0%)

5213 of 5445 relevant lines covered (95.74%)

10.34 hits per line

Relevant lines Covered
Build:
Build:
5445 RELEVANT LINES 5213 COVERED LINES
10.34 HITS PER LINE
Source Files on mysql-myisasm
  • List 0
  • Changed 7
  • Source Changed 0
  • Coverage Changed 7
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
605 mysql-myisasm Use InnoDB temp tables And truncate them. For most things this seems to speed up writes by around 10% or more due to the way the temp tables are allocated. Tested on both 5.5 and 5.7. I think the dropping was an attempt to make the tables stat... push 30 Jan 2017 09:15PM UTC jamadden travis-ci pending completion  
604 mysql-myisasm Use InnoDB temp tables And truncate them. For most things this seems to speed up writes by around 10% or more due to the way the temp tables are allocated. Tested on both 5.5 and 5.7. I think the dropping was an attempt to make the tables stat... Pull #162 30 Jan 2017 08:59PM UTC web-flow travis-ci pending completion  
603 mysql-myisasm Use InnoDB temp tables And truncate them. For most things this seems to speed up writes by around 10% or more due to the way the temp tables are allocated. Tested on both 5.5 and 5.7. I think the dropping was an attempt to make the tables stat... push 30 Jan 2017 08:53PM UTC jamadden travis-ci pending completion  
602 mysql-myisasm Use InnoDB temp tables And truncate them. For most things this seems to speed up writes by around 10% due to the way the temp tables are allocated. Tested on both 5.5 and 5.7. I think the dropping was an attempt to make the tables statement-le... push 30 Jan 2017 07:27PM UTC jamadden travis-ci pending completion  
595 mysql-myisasm Use InnoDB temp tables And truncate them. For most things this seems to speed up writes by around 10% due to the way the temp tables are allocated. Tested on both 5.5 and 5.7. I think the dropping was an attempt to make the tables statement-le... push 27 Jan 2017 11:08PM UTC jamadden travis-ci pending completion  
See All Builds (1461)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc