Skip to Content.
Sympa Menu

edugain-discuss - RE: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata

edugain-discuss AT lists.geant.org

Subject: An open discussion list for topics related to the eduGAIN interfederation service.

List archive

RE: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata


Chronological Thread 
  • From: "Cantor, Scott" <cantor.2 AT osu.edu>
  • To: Alan Buxey <alan.buxey AT myunidays.com>, Lukas Hämmerle <lukas.haemmerle AT switch.ch>
  • Cc: "edugain-discuss AT lists.geant.org" <edugain-discuss AT lists.geant.org>
  • Subject: RE: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata
  • Date: Tue, 24 Mar 2020 12:20:40 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osu.edu; dmarc=pass action=none header.from=osu.edu; dkim=pass header.d=osu.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qLNoJ/1xGVM3TzSZCpxFpeMSHCS6v8azbxq2/NShrP4=; b=JgUs+cg49Ki26kejQgS78+rhJQxOzJNwTiabXAz8g/t79izxOfaY3DrhD/h5lXYo+UEG4LRoH+XB/41dtDHUTMoFeAUURJJpA+31SvAitK6mJxJWnmYAwivryoMprf9uAStGcOanUKN7ml2zz9QIdrFP1KoBQSmapXK+/PnRTGcmtmaGnjtJWOqA1NaRRAGB5W6Gau9c9JefJiqdgq8rhIR53mbJq4AyScOaRGEVddDbo3lUtVuA/+k5gL4zhhpMXiAotRr8khKRhcBTkBKbOmTp3cbXyFUmHLoJG3sARvb7bLgGRZFDHw4qPtQrhFYRavZQenNbAjQQPiIt6u3yzQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XoUnJ9i4ogA2ZYvWOiIyfBK/d0sjUUtQ+iTPFfsuRKhswdzCGRKYnDfpH1865HKUU3DagS++ZC2eChtaE9whjJHp9AgvelDpZ37vHw5CnsO4quSVLA++dWaPyhDzXe4EFa3TAN17hBWu05Xw3uy+jbhnf/EMRVZ2n5u7ByoW7iicqBOK/LG6YNCCIqMqLbcjf/SmwycxNttBk1R4k1v5MzELT2DLsdFKE8S1MConHpEh1XnJvHu9m9lw8hwboeIsbwJSfNje2FHHoiFM/FfjwHxXEauuW7j2Po5QFDMH1QvadnVD8uBqNMVSh5qAbLA70DCVWhu5fg7Od8qf8BGoDg==
  • Authentication-results-original: spf=none (sender IP is ) smtp.mailfrom=cantor.2 AT osu.edu;

> that's another growth factor to take into account too. if people move to 4k
> certs then thats an extra 1k per entity (from their current 2048) (I know
> its not
> much per entity but adds up in an aggregate)

Just so there's some qualification around this issue, I want to note that I
tested the current 70M InCommon import aggregate as of yesterday morning on a
two year old laptop with 16 GB of RAM and total processing time was 3
minutes. It's not a multithreaded algorithm, so the number of cores doesn't
matter.

I think people need to stop running on pocket calculators and they'll find
the results really aren't that bad. Embedded systems are one thing, but
nobody should be running a server in 2020 with 4GB of RAM and if they do,
there are workarounds they can use to offload processing to other tools.

-- Scott




Archive powered by MHonArc 2.6.19.

Top of Page