user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
* [PATCH 0/6] xcpdb -index improvements
@ 2020-08-12  9:17 Eric Wong
  2020-08-12  9:17 ` [PATCH 1/6] xapcmd: simplify sub reference Eric Wong
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: Eric Wong @ 2020-08-12  9:17 UTC (permalink / raw)
  To: meta

Nothing terribly exciting, since xcpdb isn't really used often.

But it'd be bad if it flooded the system with many parallel
processes on HDD because -index was configured for many small
shards.  So now it now supports --sequential-shard and all the
other index options.

Eric Wong (6):
  xapcmd: simplify sub reference
  xcpdb: support --no-fsync from CLI
  xapcmd: reduce CPU idling when shards exceeds job count
  admin: don't warn when --jobs exceeds shards
  xcpdb: wire up new index options and --help
  v2writable: remove IdxStack import

 Documentation/public-inbox-xcpdb.pod | 19 +++++++-
 lib/PublicInbox/Admin.pm             |  4 +-
 lib/PublicInbox/V2Writable.pm        |  1 -
 lib/PublicInbox/Xapcmd.pm            | 12 +++--
 script/public-inbox-xcpdb            | 65 +++++++++++++++++++++++-----
 5 files changed, 83 insertions(+), 18 deletions(-)

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-08-12  9:17 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-12  9:17 [PATCH 0/6] xcpdb -index improvements Eric Wong
2020-08-12  9:17 ` [PATCH 1/6] xapcmd: simplify sub reference Eric Wong
2020-08-12  9:17 ` [PATCH 2/6] xcpdb: support --no-fsync from CLI Eric Wong
2020-08-12  9:17 ` [PATCH 3/6] xapcmd: reduce CPU idling when shards exceeds job count Eric Wong
2020-08-12  9:17 ` [PATCH 4/6] admin: don't warn when --jobs exceeds shards Eric Wong
2020-08-12  9:17 ` [PATCH 5/6] xcpdb: wire up new index options and --help Eric Wong
2020-08-12  9:17 ` [PATCH 6/6] v2writable: remove IdxStack import Eric Wong

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
		meta@public-inbox.org
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git