Improve the speed of multiple API requests
speed performance
If your script makes a lot of API calls for different tables, the performance (i.e. speed) may not be enough.
require 'QuickBaseClient'

qbc = QuickBase::Client.new

# get the schema for the QuickBase Community Forum
firstTime=true
2.times {

  totalTime = Time.now
  
  8.times {
    getSchemaTime = Time.now
    qbc.getSchema("bbqm84dzy")
    puts "getSchema took #{Time.now-getSchemaTime} seconds"
  }
  
  puts "\nTotal time: #{Time.now-totalTime} seconds"
  
  qbc.signOut
  qbc = QuickBase::Client.new
  qbc.cacheSchemas = true
  puts "Caching schema..." if firstTime
  firstTime = false
}

=begin

Sample output of the above script:-

getSchema took 1.438 seconds
getSchema took 0.515 seconds
getSchema took 0.5 seconds
getSchema took 0.485 seconds
getSchema took 0.515 seconds
getSchema took 0.532 seconds
getSchema took 0.484 seconds
getSchema took 0.5 seconds

Total time: 4.969 seconds
Caching schema...
getSchema took 0.515 seconds
getSchema took 0.016 seconds
getSchema took 0.015 seconds
getSchema took 0.0 seconds
getSchema took 0.016 seconds
getSchema took 0.0 seconds
getSchema took 0.016 seconds
getSchema took 0.031 seconds

Total time: 0.609 seconds

=end
'cacheSchemas' is one of the things you can do to improve performance.  Reducing the number of API requests will always improve performance.
cacheSchemas.rb
One-Click Ruby Installer for Windows Ruby wrapper for QuickBase HTTP API
Add Ingredient
Add Chef
Created on March  1, 2008 at  1:39 PM (PST). Owned by Quick Base.
Quick Base
Show fields from Show fields from Show fields from a related table
Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:
Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.

We're glad you're interested in doing more with Quickbase!

Now we need to make you official before you share apps or manage your account.

Verifying your email lets you share Quickbase with others in your company.

Your work email
Your company