In message <1358965339.4.0.483830445644.issue2550790@psf.upfronthosting.co.za> 
<1358965339.4.0.483830445644.issue2550790@psf.upfronthosting.co.za>,
David Hancock writes:
>New submission from David Hancock:
>
>(not sure what Type rfe is, sorry).

Request For Enhancement (i.e. new feature request).

> We have a tracker with about 3,000 "custcomp" (customer company)
> entries and about 35,000 issues overall. The issue.item.html
> for creating or modifying an issue loads in about 1 second, 
> but the issue.search.html takes 9 seconds. Most of that time is
> in rendering the custcomp pulldown for searching.
>
>I'd like to know how to either make this faster or replace the search
>retrieval with the item retrieval.
>
>In issue.item.html, the following is the line of interest:
>
><td tal:content="structure context/custcomp/menu">custcomp</td>
>
>And the corresponding section of issue.search.html is:
>
><tr tal:define="name string:custcomp;                                       
>                                            
>                db_klass string:custcomp;                                   
>                                            
>                db_content string:name;">
>  <th>Company:</th>
>  <td metal:use-macro="search_select"></td>
>  <td metal:use-macro="column_input"></td>
>  <td metal:use-macro="sort_input"></td>
>  <td metal:use-macro="group_input"></td>
></tr>
>
>If I simply replace search_select line with the context/custcomp/menu line,
>the select list renders very fast, but of course then the search doesn't
> work.

One thing to look at is to see what the html generated with the
original template and the modified template look like.

That may give an indication of what component is missing that stops
the two from being tied together. Then you can use actual html rather
than the macros to replicate the original components.