Firebase隊列延遲 - 性能問題

我正在使用firebase-queue來處理某些服務器端工作。當用戶註冊時，服務器將處理三項任務Firebase隊列延遲 - 性能問題

var customSpecs = { 
    'queue': { 
    'specs': { 
     'save_user_to_firebase': { 
     'in_progress_state': 'save_user_to_firebase_in_progress', 
     'finished_state': 'save_user_to_firebase_finished', 
     'retries': 3 
     }, 
     'fetch_from_third_party_API': { 
     'start_state': 'save_user_to_firebase_finished', 
     'in_progress_state': 'fetch_from_third_party_API_in_progress', 
     'finished_state': 'fetch_from_third_party_API_finished', 
     'retries': 3 
     }, 
     'save_to_google_datastore':{ 
     'start_state': 'fetch_from_third_party_API_finished', 
     'in_progress_state': 'save_to_google_datastore_finished', 
     'retries': 3 
     } 
    } 
    } 
}

我寫了沒有功能的測試代碼。爲了測試firebase隊列的性能，我記錄了每個用戶啓動save_user_to_firebase任務的時間。

第一隊

var options = { 
     'specId': 'save_user_to_firebase', 
     'numWorkers': 100 
    } 


    var saveUserQueue = new Queue({ tasksRef: taskRef, specsRef: specsObjectRef }, options, function (data, progress, resolve, reject) { 

    var t0 = process.hrtime(); 
    var testUser = data.test_user; 

    var now = new Date(); 
    console.log("started %s %d:%d:%d:%d", testUser, + now.getHours(), now.getMinutes(), now.getSeconds(), now.getMilliseconds()); 

    var t1 = process.hrtime(t0); 
    console.log("save_user_to_firebase completed in %s %ds %dms", testUser, t1[0], t1[1]/1000000 ); 

    resolve(data); 
    }

第二隊

var options = { 
    'specId': 'fetch_from_third_party_API', 
    'numWorkers': 100 
    }; 

    var fetchFromAPI = new Queue({ tasksRef: taskRef, specsRef: specsObjectRef }, options, function(data, progress, resolve, reject) { 

    var testUser = data.test_user; 
    var t0 = process.hrtime(); 
    //Add code for fetching from API 
    var t1 = process.hrtime(t0); 

    console.log("fetchFromAPI completed in %s %ds %dms", testUser, t1[0], t1[1]/1000000); 
    resolve(data); 
    });

3隊列

var options = { 
     'specId': 'save_to_google_datastore', 
     'numWorkers': 100 
    }; 


    var save_to_google_datastoreQueue = new Queue({ tasksRef: taskRef, specsRef: specsObjectRef }, options, function(data, progress, resolve, reject) { 

    var testUser = data.test_user; 

    var t0 = process.hrtime(); 

    var now = new Date(); 
    var t1 = process.hrtime(t0); 
    console.log("datastoreInsertActivitiesQueue completed %s %ds %dms",testUser, t1[0], t1[1]/1000000); 
    resolve(data); 
    })

我推40項任務，一個更新的呼叫。我爲每個隊列使用100名工人。我看到save_user_to_firebase tasks有很大的延遲。隊列中沒有任何功能。結果由上述代碼生成。

我測量每個用戶的save_user_to_firebase與第一個用戶在隊列中的時間之間的時間差。

started user1 at 13:5:13:575 
…… 
started user40 at 13:5:34:545

我寫了一個腳本來解析日誌並計算每個用戶的延遲。以下是輸出：

user1 delay = 0:0 
user3 delay = 0:0 
user4 delay = 0:0 
user5 delay = 0:1 
user6 delay = 0:2 
user7 delay = 0:2 
user2 delay = 0:2 
user9 delay = 0:3 
user10 delay = 0:4 
user11 delay = 0:4 
user12 delay = 0:5 
user13 delay = 0:5 
user14 delay = 0:6 
user8 delay = 0:7 
user16 delay = 0:7 
user15 delay = 0:8 
user18 delay = 0:9 
user19 delay = 0:10 
user20 delay = 0:10 
user21 delay = 0:11 
user22 delay = 0:12 
user17 delay = 0:12 
user24 delay = 0:13 
user23 delay = 0:13 
user26 delay = 0:14 
user27 delay = 0:14 
user28 delay = 0:14 
user29 delay = 0:15 
user30 delay = 0:16 
user25 delay = 0:16 
user32 delay = 0:17 
user31 delay = 0:17 
user34 delay = 0:18 
user35 delay = 0:18 
user36 delay = 0:18 
user37 delay = 0:19 
user38 delay = 0:20 
user33 delay = 0:21 
user40 delay = 0:20 
user39 delay = 0:21

這是正常的性能比率嗎？

來源

2017-03-03 Bill Dani

Firebase隊列庫使用Firebase數據庫事務來確保只有一個工作進程可以抓取任務。這意味着最大吞吐量在很大程度上取決於任務的大小。你擁有的工作人員越多，任務越短，競爭就會越高。對於短期任務，我們建議不要使用超過六名工人。之後，您將看到吞吐量增長水平下降，甚至可能下降。

來源

2017-03-03 15:04:56

Firebase隊列延遲 - 性能問題

回答

相關問題