Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#2286 closed bug (fixed)

Too many MIME updates on MIME type creation

Reported by: axeld Owned by: bonefish
Priority: normal Milestone: R1
Component: Servers/registrar Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

The registrar sends out tons of B_META_MIME_CHANGED notices when new MIME types are installed - this should be calmed down to an acceptable number, possibly just one.

Change History (5)

comment:1 Changed 11 years ago by diver

Could this be related to bug #257?

comment:2 Changed 11 years ago by axeld

Yes, probably - but since the delay is now much shorter, the problem should be gone if that was it.

comment:3 Changed 11 years ago by bonefish

Status: newassigned

comment:4 Changed 11 years ago by bonefish

Resolution: fixed
Status: assignedclosed

Actually there weren't that many notifications sent. Usually just one "created" notification and a few "updates" (one for each set property). As of hrev25730 we only send the "created" notification in such cases. For the first boot that reduces the number of sent messages from some 320 to 109. There still are a handful of unavoidable duplicates (for the servers that are started before the mimeset script runs), but other than that there really are that many MIME types involved.

comment:5 Changed 11 years ago by axeld

I think reducing the number of messages by two thirds is rather nice. But I think we may want to rethink the whole port limitations at one point anyway. For one, they really should use pageable memory to reduce the memory pressure they may currently impose when ports aren't emptied.

Note: See TracTickets for help on using tickets.