1. I have corrected the e-mail settings so that outgoing e-mails from these forums should be sent now. If you tried to Register or Reset your Password, please try again!
    Dismiss Notice

Gateway Timeouts - Possible index issues

Discussion in 'Census: General Discussion' started by Lempo, Feb 6, 2012.

  1. Lempo

    Lempo Guest

    READ BELOW BEFORE THRASHING SERVERS :)

    [url="census.daybreakgames.com/xml/get/eq2/item/?c:count=1"><span style="text-decoration: underline;"><span style="color: #0066cc;">census.daybreakgames.com/xml/get/eq2/item/?c:count=1[/url]

    [url="census.daybreakgames.com/xml/get/eq2/item/?type=Spell%20Scroll&c:count=1">census.daybreakgames.com/xml/get/eq2/ite...croll&c:count=1[/url]

    Just curious as to the total item count I tried the first command which seemed to give the server a pretty good thrashing but it finall did return a value , which I forgot (lol) then I tried the second command and got a gateway timeout.

    I know there are some memory issues right now and that there is work being done on a server farm for this project.

    I would think that both of those searches should utilize an index, and wouldn't think either would well over a minute.

     
  2. feldon30

    feldon30 Guest

    I don't know what's going on, but the server is totally hammered right now. <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" />
     
  3. Lempo

    Lempo Guest

    [url="census.daybreakgames.com/xml/count/eq2/item/">/xml/count/eq2/item/[/url]

    Tried this and got same results, left the qualifier off so it couldn't be clicked.

    I only tried these in 5 different ways max.

    Dan mentioned a RAM upgrade, which could make all the difference in the world, just being short a few K can be drastic to performance.

    I'm not going to try anything else like this (knowingly) until we get some confirmation.

    Dan just request 4X the amount of memory you need, that way when they haggle you down to 1/2 that and only give you half of whay they said they would you'll be good to go. :)

     
  4. DanKinney

    DanKinney Guest

    Yeah...I'm trying.

    The c:count=1 feature is very nice and useful, but it is probably the source of the timeout.  Even though your request maybe fulfilled rather quickly, the c:count=1 will continue the query to its completion to see how many object could have been returned. On an un-indexed field, that is death.

    Our mid-to-long term goal is that the entire database will be in-memory resident.  That is simply how it needs to be. 

    -dan

     

Share This Page