Page Comparison

...

No code was added to the actions (no tests were run) to determine actual memory use of each call. List domain

listdomain Action

...

    Parameters —

             name &actor
               string &fio_domain
               uint64_t &sale_price
               uint64uint64_t &max_fee
               string &tpid

...

Based on this output the account wjeo4abnk4c2 requires 755 bytes of RAM. Using the standard formula of usage x 1.5 I am increasing the ram by 1140 bytes rounding up a little from 755x1.5.

cxlistdomain

...

Action

       Parameters —

              name &actor,
               string &fio_domain,
               int64_t &max_fee,
               string &tpid

...

This removes the RAM from the user account and increases on fio.escrow so it seems like no RAM bump is required at all.   Buy domain

buydomain Action

        Parameters —

               name &actor, const int64_t &sale_id,
               string &fio_domain, const int64_t &max_buy_price,
               int64_t &max_fee, const string &tpid

...

           Recommendation — reduce RAM bump to be 256 on this call.

Ram Analysis by Thomas

Similar to cxlistdoman ram usage is removed from the user and added to the fio.escrow account:

"account_ram_deltas": [
  {
    "account": "fio.

...

escrow",
    "delta": 466
  },
  {
    "account": "wjeo4abnk4c2",
    "delta": -466
  }
],

Set Marketplace config (setmrkplcfg) Action

              Tables updated
                   mrkplconfigs row added

...

When looking at the response object of a setmrkplcfg action, there are no ram_deltas even though I am changing settings.

cxburned

...

action

           Only called by a FIO system contract (with unlimited resources) no ram bump needed….

...