[
https://issues.apache.org/jira/browse/OODT-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969347#action_12969347
]
Chris A. Mattmann commented on OODT-68:
---------------------------------------
bq. on NPP PEATE we have like 400,000 IASI products, which translates to like
400,000x20 rows in the metadata table (where 20 is the number metadata fields
per product) . . . this table continues to grow
On OCO, at current count, we've got about 700K GOSATL1bFTS products. I just
loaded up the ops UI to test this and the page loaded in ~5-10 secs.
On WRM, we've got 9B data point rows across a number of database tables in
MySQL and we're able to query them in < 30 seconds
bq. typically the filemgr (using Oracle DB in this case) is being hit by
workflow condition queries at the same time . . . 20 seconds is not bad when
all that is taken into consideration
One possible mitigation for this would be to stand up a read-only filemgr to
load balance the queries to the underlying Oracle DB. This was something I was
considering doing on OCO because I didn't want the single filemgr used for
processing to get bogged down when an operator wanted to check status as well.
Since the only cost is another port taken and a service up and running (with
some allocated # of threads), I think it's a small cost to pay to increase some
of the performance aspects you're seeing on PEATE.
bq. i'm only adding two methods (won't touch the other methods in ProductPage)
. . . would be a new member variable and a setter and getter for that variable
(i.e. numOfHits, setNumOfHits(int), getNumOfHits() respectively) . . . then the
Catalogs would be modified to use the setter method.
I'm just wondering why we have to add any methods at all. I'm not sure I see
the pressing need for changing this API.
> Add Number of Product Hits to ProductPage
> -----------------------------------------
>
> Key: OODT-68
> URL: https://issues.apache.org/jira/browse/OODT-68
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - By adding get number of hits the method setTotalPages(int) is no longer
> needed; getTotalPages will calculate its return value based on page size and
> total hits
> - This also allows the number of products to be determined by just getting
> the first page, instead of getting last page which internally requires
> DataSourceCatalog to get first page and last page
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
