Modify

Ticket #755 (closed task: fixed)

Opened 2 years ago

Last modified 2 years ago

WSGI setup

Reported by: anna Owned by:
Priority: critical Milestone: 4.4 .Beta - Video Publishing
Component: Architecture Severity:
Keywords: Cc:
Who will test this: And

Description

Noting some results from testing new wsgi setup for 4.4 here.

Attachments

Change History

comment:1 Changed 2 years ago by anna

This may be unrelated, but noting that front page of wsgi.engagemedia.org seemed to load slowly - blank page for ages then it loaded.

unknown68a86d4c6a32:etc anna$ ping wsgi.engagemedia.org PING komo1.engagemedia.org (176.9.67.213): 56 data bytes 64 bytes from 176.9.67.213: icmp_seq=0 ttl=44 time=256.101 ms 64 bytes from 176.9.67.213: icmp_seq=1 ttl=44 time=230.598 ms 64 bytes from 176.9.67.213: icmp_seq=2 ttl=44 time=387.333 ms 64 bytes from 176.9.67.213: icmp_seq=3 ttl=44 time=615.316 ms 64 bytes from 176.9.67.213: icmp_seq=4 ttl=44 time=335.727 ms C --- komo1.engagemedia.org ping statistics --- 6 packets transmitted, 5 packets received, 16.7% packet loss

comment:2 Changed 2 years ago by anna

successful video upload. did take a long time, but i'm not necessarily on a fast connection here.

comment:3 Changed 2 years ago by dimo

The tagcloud generation takes time for the first time each instance is accessed. Subsequent requests are served a lot faster because the result is cached. That's true for the existing em.org as well. It would make a lot of sense to refactor the tagcloud portlet in order to persist the cached result in the ZODB as well and to update the tags asynchronously using plone.app.async, but that's probably something for 4.5 or 4.4.1

comment:4 Changed 2 years ago by anna

Have ticketed tagcloud issue here:  https://plumi.org/ticket/764

comment:5 Changed 2 years ago by dimo

  • Status changed from new to closed
  • Resolution set to fixed

We're ok here. If we discover any issues when we deploy for production let's ticket them separately.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.